mcp-mssql

Run SQL (safe)

run_sql_safe

Run SELECT-only queries on MSSQL databases with automatic TOP limits, preventing DDL/DML changes and excessive data retrieval.

Instructions

Yalnızca tek SELECT ifadesi çalıştırır; DDL/DML yasak; TOP limiti otomatik enjekte edilir.

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": "<sql>"
    },
    "name": "run_sql_safe"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals important traits: it only permits a single SELECT, rejects DDL/DML, and automatically injects a TOP limit. These details go beyond a generic 'runs SQL' and give the agent a clear safety and modification profile.

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, efficient sentence in Turkish that delivers all need-to-know information without extraneous words. Its structure is ideal for quick agent parsing.

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

Completeness4/5

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

For a tool with one simple parameter, no output schema, and no annotations, the description covers the essential constraints and behavior. It lacks examples or output format details, but these are not critical for an agent to correctly invoke a straightforward SELECT execution tool.

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

Parameters5/5

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

The description adds substantial meaning to the 'sql' parameter, which has zero schema coverage. It specifies the parameter must be a single SELECT statement, forbids DDL/DML, and notes the automatic TOP injection. This fully compensates for the lack of schema descriptions.

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 clearly states the tool's function with a specific verb and resource: 'Yalnızca tek SELECT ifadesi çalıştırır' (executes only a single SELECT statement). It distinguishes itself from siblings by explicitly limiting scope to SELECT and forbidding DDL/DML, making its purpose unmistakable.

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

Usage Guidelines4/5

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

The description gives clear context about when to use the tool (for read-only SELECT queries) and explicitly excludes DDL/DML. However, it does not explicitly name alternative tools like connect_db or discover_schema, so it falls short of a 5 but provides better guidance than an implicit usage.

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

Deploy Server