mcp-sqlserver

get_execution_plan

Read-only

Analyze SQL Server queries by retrieving their execution plans. Provide a connection and SQL query to identify performance bottlenecks and optimize indexing.

Instructions

Get execution plan for a query

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connection": "<connection>",
      "sql": "<sql>"
    },
    "name": "get_execution_plan"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	Yes	SQL query to analyze
`connection`	Yes	Connection name to use

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Sep 10, 2026

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotation readOnlyHint=true already covers the read-only nature. The description adds no extra behavioral context such as whether the query is actually executed, permission requirements, or return behavior. It does not contradict the annotation, but it offers no additional transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no filler or redundant phrases. Every word contributes to the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description is extremely sparse. It does not explain what an execution plan contains, how the result is presented, or how this tool differs from running a query. An agent must infer critical details from the tool name and siblings, which is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both sql and connection already clearly documented. The description's 'query' loosely maps to the sql parameter but adds no new meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get execution plan for a query' uses a specific verb and resource, clearly identifying what the tool does. It is distinct from siblings like query (executes) and get_schema, so an agent can select it correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as query, and does not clarify that this tool analyzes rather than executes the query. There are no exclusions or conditions to help route the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server