Skip to main content
Glama
dhipskind253

mssql-mcp

by dhipskind253

list_procedures

Retrieve stored procedures from a Microsoft SQL Server database, optionally filtered by schema. Supports database exploration and understanding via natural language.

Instructions

List stored procedures, optionally filtered by schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaNo

Implementation Reference

  • The actual execution logic: queries sys.procedures with optional schema filtering.
    async listProcedures(schema?: string) {
      const r = await (await this.getPool())
        .request()
        .input('schema', sql.NVarChar, schema ?? null).query(`
          SELECT s.name AS schema_name, p.name AS procedure_name
          FROM sys.procedures p
          INNER JOIN sys.schemas s ON p.schema_id = s.schema_id
          WHERE (@schema IS NULL OR s.name = @schema)
          ORDER BY s.name, p.name
        `);
      return r.recordset;
  • src/index.ts:133-140 (registration)
    Registers the 'list_procedures' tool with MCP server, defining description and schema.
    server.tool(
      'list_procedures',
      'List stored procedures, optionally filtered by schema.',
      {
        schema: z.string().optional(),
      },
      async ({ schema }) => runTool(() => db.listProcedures(schema))
    );
  • Input schema for list_procedures: optional schema filter string.
    {
      schema: z.string().optional(),
Behavior2/5

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

No annotations exist, so the description must disclose behaviors. It only states basic functionality and omits details like read-only nature, potential cost, pagination, or response format.

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?

Very short and front-loaded, but perhaps too brief. It efficiently conveys the core functionality without extra words.

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 tool with one optional parameter, the description is adequate but lacks details on output format, sorting, or limits. The absence of an output schema heightens the need for more description.

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?

With 0% schema description coverage, the description adds minimal meaning by mentioning 'optionally filtered by schema', but doesn't explain the parameter's format or accepted values beyond what the type implies.

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 lists stored procedures with optional schema filtering. It distinguishes itself from sibling list tools by specifying the resource type (procedures).

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 on when to use this vs alternative tools like get_procedure_definition or other list tools. The description fails to provide context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dhipskind253/mssql-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server