Skip to main content
Glama

server_info

Retrieve information about the db-mcp server and its registered database adapters to understand available database connections and configurations.

Instructions

Get information about the db-mcp server and registered adapters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'server_info' tool. It iterates over registered database adapters, collects their info, and returns a JSON string containing server name, version, transport type, list of adapters, and tool filter summary.
        () => {
            const adapterInfo = [];
            for (const [id, adapter] of this.adapters) {
                adapterInfo.push({
                    id,
                    ...adapter.getInfo()
                });
            }
    
            return {
                content: [{
                    type: 'text' as const,
                    text: JSON.stringify({
                        name: this.config.name,
                        version: this.config.version,
                        transport: this.config.transport,
                        adapters: adapterInfo,
                        toolFilter: {
                            raw: this.toolFilter.raw,
                            enabledCount: this.toolFilter.enabledTools.size
                        }
                    }, null, 2)
                }]
            };
        }
    );
  • Registration of the 'server_info' tool on the MCP server using the deprecated server.tool method. Includes name, description, empty input schema, and inline handler function.
    this.server.tool(
        'server_info',
        'Get information about the db-mcp server and registered adapters',
        {},
        () => {
            const adapterInfo = [];
            for (const [id, adapter] of this.adapters) {
                adapterInfo.push({
                    id,
                    ...adapter.getInfo()
                });
            }
    
            return {
                content: [{
                    type: 'text' as const,
                    text: JSON.stringify({
                        name: this.config.name,
                        version: this.config.version,
                        transport: this.config.transport,
                        adapters: adapterInfo,
                        toolFilter: {
                            raw: this.toolFilter.raw,
                            enabledCount: this.toolFilter.enabledTools.size
                        }
                    }, null, 2)
                }]
            };
        }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying a read-only operation, but doesn't specify what information is included (e.g., server version, adapter details), response format, or potential limitations like rate constraints. This leaves significant gaps for a tool with no 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, efficient sentence that directly states the tool's purpose without redundancy or fluff. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 simplicity (0 parameters, no annotations, no output schema), the description is adequate as a minimum viable explanation. However, it lacks details on what specific information is returned (e.g., server metadata, adapter configurations), which could help the agent understand the output better. Without an output schema, the description should ideally hint at the response structure.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate, earning a baseline score of 4 for not introducing unnecessary complexity.

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 tool's purpose with a specific verb ('Get') and resource ('information about the db-mcp server and registered adapters'). It distinguishes from siblings like 'list_adapters' (which likely lists adapters only) and 'server_health' (which likely checks health status), though it doesn't explicitly mention these distinctions.

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 'list_adapters' or 'server_health'. It doesn't specify use cases, 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

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/neverinfamous/db-mcp'

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