Skip to main content
Glama
Sign In
MSSQL MCP Reader

MSSQL MCP Reader

by ConnorBritain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

run_script

Execute a pre-approved SQL script by name with custom parameters. Use list_scripts to see available templates.

Instructions

Executes a named SQL script with parameters. Scripts are pre-approved SQL templates. Use list_scripts to see available scripts.

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": {
      "scriptName": "<scriptName>"
    },
    "name": "run_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptNameYesName of the script to execute (from list_scripts)
parametersNoParameter values for the script (key-value pairs)
previewNoIf true, shows the resolved SQL without executing. Default: false
confirmNoRequired for scripts with requiresApproval or in environments with requireApproval. Set to true after reviewing preview.
environmentNoTarget environment (optional, uses default if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.1/5.0
Behavior4/5

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

Discloses scripts are pre-approved, mentions preview shows SQL without execution, and confirm parameter is required for approval. No annotations provided, so description carries burden; however, does not detail return format or transaction behavior.

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?

Two concise sentences, no fluff, front-loaded with key action and resource.

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?

Covers safety preview/confirm but omits what the tool returns (e.g., result rows, success message). No output schema, so description should fill gap. Incomplete for a SQL execution tool.

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?

All 5 parameters have schema descriptions (100% coverage). Description adds no extra meaning beyond 'with parameters'; schema already explains each parameter adequately.

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?

Clearly states 'Executes a named SQL script with parameters' and notes scripts are pre-approved templates. Distinguishes from siblings by specifying use of list_scripts to see available scripts.

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?

Refers to list_scripts for available scripts and implies use of preview/confirm for safety. Does not explicitly contrast with sibling tools like read_data or explain_query.

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

Deploy Server

Other Tools