SQL Server MCP Server

execute_sql

Run arbitrary T-SQL statements, including DDL and DML, to create, alter, drop, insert, update, or delete database objects and data.

Instructions

Execute arbitrary SQL statements such as DDL (CREATE, ALTER, DROP) or DML (INSERT, UPDATE, DELETE).

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": {
      "sql_statement": "<sql_statement>"
    },
    "name": "execute_sql"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No	Positional parameter values for query placeholders (?).
`sql_statement`	Yes	T-SQL statement to execute.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 19, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description only lists DDL/DML categories without disclosing safety-relevant behavior such as irreversibility, lack of validation, or the ability to affect schema/data arbitrarily. Since annotations are absent, the description carries the full burden and under-delivers.

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, front-loaded sentence that names the operation, the resource, and representative sub-actions. Every word contributes value, with no filler or redundancy.

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

Completeness3/5

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

For a high-flexibility arbitrary SQL tool, the description is minimally adequate but omits guidance on side effects, alternatives, or execution behavior beyond the raw examples. The presence of an output schema reduces the need to document return values, but the overall context is thin.

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%, so both parameters are already well documented by the input schema. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Execute') with a clear resource ('arbitrary SQL statements') and enumerates DDL/DML examples. This differentiates it from the narrow sibling tools like insert_record or read_records.

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

Usage Guidelines3/5

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

The phrase 'arbitrary SQL statements' and the DDL/DML examples imply a general-purpose fallback, but the description does not explicitly state when to prefer dedicated sibling tools (e.g., insert_record, update_records) or when not to use execute_sql. This is implied usage rather than explicit guidance.

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

Deploy Server