Skip to main content
Glama
cwilby

SQL Server MCP

by cwilby

get-tables

Retrieve a comprehensive list of all tables within a Microsoft SQL Server database using the MCP server, enabling efficient database exploration and management.

Instructions

Get a list of all tables in the database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implements the core logic for the 'get-tables' tool by querying INFORMATION_SCHEMA.TABLES to retrieve and return a list of base tables in the database.
    async getTables() {
        const tables = await database.query(`
            SELECT TABLE_NAME, TABLE_TYPE
            FROM INFORMATION_SCHEMA.TABLES
            WHERE TABLE_TYPE = 'BASE TABLE'
        `);
    
        if (!tables.length) return this.toResult("No tables found in the database.");
    
        return this.toResult(`Tables found in the database:\n${JSON.stringify(tables)}`);
    }
  • Registers the 'get-tables' tool with the MCP server, providing its name, description, and binding it to the getTables handler method.
    server.tool(
        "get-tables",
        "Get a list of all tables in the database",
        tools.getTables.bind(tools)
    );
Behavior2/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 states this is a read operation ('Get'), implying it's likely safe and non-destructive, but doesn't specify permissions needed, rate limits, pagination behavior, or what the returned list includes (e.g., table names, metadata). This leaves significant gaps for a tool with zero annotation coverage.

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, clear sentence that efficiently conveys the core purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool, earning full marks for conciseness and structure.

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?

Given the tool's low complexity (0 parameters, no output schema) and the description's clear purpose, it's minimally adequate. However, with no annotations and no output schema, it lacks details on behavioral traits (e.g., permissions, return format) that would help an agent use it correctly, making it incomplete for optimal agent guidance.

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

Parameters4/5

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

The input schema has 0 parameters with 100% description coverage, so the schema fully documents the lack of inputs. The description implicitly confirms this by not mentioning any parameters, adding no extra semantic detail but aligning with the schema. A baseline of 4 is appropriate for zero-parameter tools where the schema already covers everything.

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 clearly states the verb ('Get') and resource ('list of all tables in the database'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'get-table', which retrieves a single table, so it misses the highest score for sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like 'get-table' (for a single table) or 'query' (for executing SQL queries). It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage from the purpose alone.

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

Related 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/cwilby/mcp-node-mssql'

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