MCP Prompts

mcilspy includes two MCP prompts that provide structured analysis workflows. Prompts are templates that MCP clients can invoke to guide multi-step analysis — they tell the AI assistant what tools to call and in what order.

analyze_assembly

A structured prompt for broad assembly analysis. It walks the assistant through discovering the overall structure, key types, namespaces, and architectural patterns.

Parameters

Parameter	Type	Required	Default	Description
`assembly_path`	`string`	Yes	—	Path to the `.dll` or `.exe` to analyze
`focus_area`	`string`	No	`"types"`	What to focus on: `types`, `namespaces`, or `dependencies`

What It Does

The prompt instructs the assistant to:

Examine the overall structure and organization of the assembly
Identify key types and their relationships
Map out namespaces and their purposes
Note architectural patterns and design decisions

The focus_area parameter steers the analysis toward types, namespace organization, or dependency relationships.

{
  "method": "prompts/get",
  "params": {
    "name": "analyze_assembly_prompt",
    "arguments": {
      "assembly_path": "/path/to/MyApp.dll",
      "focus_area": "namespaces"
    }
  }
}

Generated Prompt

I need to analyze the .NET assembly at "/path/to/MyApp.dll".

Please help me understand:
1. The overall structure and organization of the assembly
2. Key types and their relationships
3. Main namespaces and their purposes
4. Any notable patterns or architectural decisions

Focus area: namespaces

Start by listing the types in the assembly, then provide insights
based on what you find.

decompile_and_explain

A targeted prompt for deep-diving into a specific type. It instructs the assistant to decompile the type and provide a thorough explanation of its implementation.

Parameters

Parameter	Type	Required	Default	Description
`assembly_path`	`string`	Yes	—	Path to the `.dll` or `.exe` containing the type
`type_name`	`string`	Yes	—	Fully qualified or short name of the type to analyze

What It Does

The prompt instructs the assistant to:

Decompile the specified type to C# source code
Explain what the type does and its purpose
Highlight interesting patterns, design decisions, or potential issues
Suggest how the type fits into the overall architecture

Example Request

JSON-RPC
Natural Language

{
  "method": "prompts/get",
  "params": {
    "name": "decompile_and_explain_prompt",
    "arguments": {
      "assembly_path": "/path/to/MyApp.dll",
      "type_name": "MyApp.Services.AuthService"
    }
  }
}

Generated Prompt

I want to understand the type "MyApp.Services.AuthService" from
the assembly "/path/to/MyApp.dll".

Please:
1. Decompile this specific type
2. Explain what this type does and its purpose
3. Highlight any interesting patterns, design decisions, or
   potential issues
4. Suggest how this type fits into the overall architecture

Type to analyze: MyApp.Services.AuthService
Assembly: /path/to/MyApp.dll

Using Prompts

How you invoke MCP prompts depends on your client.

Claude Code and Claude Desktop surface prompts automatically. You can reference them by name in natural language:

“Run the analyze_assembly prompt on /path/to/MyApp.dll”

Programmatic clients use the prompts/get JSON-RPC method, passing the prompt name and arguments as shown in the examples above. The client receives the expanded text and can include it as part of a conversation.