Skip to main content
Glama
Sign In
mcp-sqlserver

mcp-sqlserver

by cvelasquez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_stored_procedure

Read-only

Retrieve the definition or source code of a stored procedure from a specified SQL Server connection. Use connection name and procedure name to get the exact SQL text.

Instructions

Get stored procedure definition

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

Input Schema

NameRequiredDescriptionDefault
nameYesStored procedure name
connectionYesConnection name to use

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already signals a safe read operation, and the description adds no further behavioral context. It does not describe what 'definition' includes, whether it returns SQL text, what happens if the procedure does not exist, or any permission requirements.

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

Conciseness4/5

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

The description is extremely short, with no filler or redundant phrasing. It front-loads the core purpose effectively, though it could be expanded slightly without losing its concise character.

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 simple two-parameter read-only tool, the definition is minimally viable: the parameters are fully documented and the readOnlyHint covers safety. However, with no output schema and no return-value description, the agent is left guessing about the exact shape or content of the returned definition.

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 already provides full descriptions for both required parameters (name and connection), so the description does not need to repeat them. It also adds no extra meaning beyond the schema, which is why the 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 states a clear verb and resource: it retrieves the stored procedure definition. It is unambiguous about which object it targets and is distinguishable from siblings like get_schema or get_indexes, though it does not explicitly contrast itself with them.

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 gives no guidance on when to use this tool versus alternatives such as query or get_execution_plan. There is no mention of prerequisites, exclusions, or typical scenarios, so the agent must infer usage from the name alone.

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