MCP MS SQL Server

execute_sql_query

Execute SQL queries on a Microsoft SQL Server database using optional parameters for prepared statements.

Instructions

Execute a SQL query against the MS SQL Server database

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": {
      "query": "<query>"
    },
    "name": "execute_sql_query"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	The SQL query to execute
`parameters`	No	Optional parameters for prepared statements

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Without annotations, the description carries the full burden of disclosing behavioral traits. It only says 'execute', which implies both read and write operations, but does not mention side effects, transaction safety, error behavior, or permissions. This is insufficient for a powerful SQL execution tool.

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

Conciseness3/5

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

The description is a single sentence with no unnecessary words, but it is overly terse for a tool that executes arbitrary SQL. It could include essential context without being verbose, so it is acceptable but not excellent.

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

Completeness1/5

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

Given the complexity of SQL execution (potential for data modification, no output schema, no annotations), the description is woefully incomplete. It lacks information on return values, error handling, query types allowed, and safety considerations.

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?

The input schema provides descriptions for both parameters (query and parameters), achieving 100% schema description coverage. The description adds no further meaning beyond the schema, so a baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the verb 'Execute' and the resource 'SQL query against the MS SQL Server database', making the purpose clear. However, it does not distinguish itself from sibling tools like describe_table or list_tables, but the action is fundamentally different so no explicit differentiation is critical.

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?

No guidance is provided on when to use this tool versus alternatives, nor any caution about using SQL queries that modify data. The description lacks any contextual advice that would help an agent decide when this tool is appropriate.

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

Deploy Server