Skip to main content
Glama

Get Server Information

get-server-info

Retrieve server information and list available tools for the MCP Firebird server to understand capabilities and configuration.

Instructions

Obtiene información sobre el servidor MCP Firebird y las herramientas disponibles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the get-server-info tool that returns server metadata including name, version, capabilities (available DB tools), and runtime info (Node version, platform, uptime, memory usage). Uses formatForClaude to format the response.
    tools.set('get-server-info', {
        title: 'Get Server Information',
        description: 'Obtiene información sobre el servidor MCP Firebird y las herramientas disponibles',
        inputSchema: z.object({}),
        handler: async () => {
            try {
                const serverInfo = {
                    name: pkg.name || 'MCP Firebird Server',
                    version: pkg.version || '2.6.0-alpha.11',
                    description: pkg.description || 'Servidor MCP para bases de datos Firebird',
                    capabilities: {
                        tools: Array.from(databaseTools.keys()),
                        totalTools: databaseTools.size,
                        features: [
                            'SQL query execution',
                            'Database schema inspection',
                            'Performance analysis',
                            'Backup and restore',
                            'Database validation'
                        ]
                    },
                    runtime: {
                        nodeVersion: process.version,
                        platform: process.platform,
                        uptime: process.uptime(),
                        memoryUsage: process.memoryUsage()
                    }
                };
    
                return {
                    content: [{
                        type: 'text',
                        text: `Información del servidor MCP Firebird:\n\n${formatForClaude(serverInfo)}`
                    }]
                };
            } catch (error) {
                logger.error('Error getting server info:', { error });
                return {
                    content: [{
                        type: 'text',
                        text: `Error obteniendo información del servidor: ${error instanceof Error ? error.message : String(error)}`
                    }],
                    isError: true
                };
            }
        }
    });
  • Input schema for get-server-info: takes no arguments (empty Zod object).
    inputSchema: z.object({}),
  • Registration of get-server-info within the setupMetadataTools function. The tool is registered in a Map under the name 'get-server-info'. setupMetadataTools is called from multiple server entry points (smithery-entry.ts, http-entry.ts, smithery.ts, create-server.ts, index.ts, mcp-server.ts).
    export function setupMetadataTools(databaseTools: Map<string, any>): Map<string, ToolDefinition> {
        const tools = new Map<string, ToolDefinition>();
  • The formatForClaude helper used by the handler to pretty-print the server info object as JSON.
    export const formatForClaude = (result: any): string => {
        try {
            // For simple strings, return them directly
            if (typeof result === 'string') {
                return result;
            }
    
            // For objects, convert them to a pretty JSON string
            return JSON.stringify(result, null, 2);
        } catch (error) {
            // Handle JSON.stringify errors
            console.error(`Error formatting for Claude: ${error instanceof Error ? error.message : String(error)}`);
            return `Error formatting result: ${error instanceof Error ? error.message : String(error)}`;
        }
    };
  • Reads package.json at module load time to extract server name, version, and description used by the get-server-info handler.
    const __filename = fileURLToPath(import.meta.url);
    const __dirname = dirname(__filename);
    const packageJsonPath = join(__dirname, '../../package.json');
    const pkg = JSON.parse(readFileSync(packageJsonPath, 'utf-8'));
Behavior3/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. It states the tool returns server info and tool availability but does not disclose any behavioral traits (e.g., auth requirements, rate limits). For a simple info tool, this is adequate but could be expanded.

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 sentence, front-loaded with the purpose, and contains no superfluous information. Every word contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description could specify what 'información' includes (e.g., version, uptime). However, for a server info tool, the description is mostly complete given the context.

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?

There are zero parameters, so schema coverage is 100%. The description adds no parameter info, but none is needed. Baseline score of 4 applies for no parameters.

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 retrieves information about the MCP Firebird server and available tools. It uses a specific verb ('obtiene') and resource ('información sobre el servidor'), distinguishing it from sibling tools that focus on specific database operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for general server info but does not explicitly state when to use it versus alternatives like 'list-available-tools' or 'get-database-info'. No guidance on when not to use it.

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/PuroDelphi/mcpFirebird'

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