Skip to main content
Glama

Get Server Information

get-server-info

Retrieve details about the MCP Firebird server and its available tools to understand database access capabilities.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The asynchronous handler function that executes the 'get-server-info' tool. It retrieves package information from package.json, lists available database tools, collects runtime statistics, and returns formatted server information or an error response.
    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
            };
        }
    }
  • The input schema for the 'get-server-info' tool, defined as an empty Zod object schema indicating no input parameters are required.
    inputSchema: z.object({}),
  • The registration of the 'get-server-info' tool in the setupMetadataTools function, including title, description, schema, and inline handler.
    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
                };
            }
        }
    });
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 details like whether it requires authentication, returns structured or unstructured data, has rate limits, or provides error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 in Spanish that directly states the tool's purpose without redundancy or fluff. It's front-loaded with the core action and resources, 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 output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits and usage context, which are important for an agent to operate effectively. With no output schema, it doesn't explain return values, but for a low-complexity tool, this is acceptable though not ideal.

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% coverage, so no parameter information is needed. The description doesn't mention parameters, which is appropriate. Baseline is 4 for zero parameters, as it avoids unnecessary details.

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 in Spanish ('Obtiene información sobre el servidor MCP Firebird y las herramientas disponibles'), which translates to 'Gets information about the MCP Firebird server and available tools.' This specifies the verb ('gets') and resources ('server information' and 'available tools'), but doesn't explicitly differentiate it from sibling tools like 'get-database-info' or 'list-available-tools' that might overlap in scope.

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. With siblings like 'get-database-info' (for database-specific details) and 'list-available-tools' (for listing tools), there's potential overlap, but the description doesn't clarify distinctions, exclusions, or prerequisites for usage.

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