Skip to main content
Glama

List Available Tools

list-available-tools

Discover available tools in the MCP Firebird server to access, analyze, and manipulate Firebird SQL databases through natural language.

Instructions

Lista todas las herramientas disponibles en el servidor MCP

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFiltrar por categoría (database, metadata)

Implementation Reference

  • The core handler function that lists all available database and metadata tools, optionally filtered by 'category' (database or metadata), and returns formatted text output.
    handler: async (args: { category?: string }) => {
        try {
            const allTools = new Map([...databaseTools, ...tools]);
            let toolsList = Array.from(allTools.entries());
    
            if (args.category) {
                if (args.category === 'database') {
                    toolsList = Array.from(databaseTools.entries());
                } else if (args.category === 'metadata') {
                    toolsList = Array.from(tools.entries());
                }
            }
    
            const toolsInfo = toolsList.map(([name, tool]) => ({
                name,
                title: tool.title || name,
                description: tool.description,
                category: databaseTools.has(name) ? 'database' : 'metadata'
            }));
    
            return {
                content: [{
                    type: 'text',
                    text: `Herramientas disponibles${args.category ? ` (categoría: ${args.category})` : ''}:\n\n${formatForClaude(toolsInfo)}`
                }]
            };
        } catch (error) {
            logger.error('Error listing tools:', { error });
            return {
                content: [{
                    type: 'text',
                    text: `Error listando herramientas: ${error instanceof Error ? error.message : String(error)}`
                }],
                isError: true
            };
        }
    }
  • Zod schema defining the optional 'category' input parameter for filtering tools.
    inputSchema: z.object({
        category: z.string().optional().describe('Filtrar por categoría (database, metadata)')
    }),
  • Registers the 'list-available-tools' tool definition (including inline handler and schema) in the metadata tools Map returned by setupMetadataTools.
    tools.set('list-available-tools', {
        title: 'List Available Tools',
        description: 'Lista todas las herramientas disponibles en el servidor MCP',
        inputSchema: z.object({
            category: z.string().optional().describe('Filtrar por categoría (database, metadata)')
        }),
        handler: async (args: { category?: string }) => {
            try {
                const allTools = new Map([...databaseTools, ...tools]);
                let toolsList = Array.from(allTools.entries());
    
                if (args.category) {
                    if (args.category === 'database') {
                        toolsList = Array.from(databaseTools.entries());
                    } else if (args.category === 'metadata') {
                        toolsList = Array.from(tools.entries());
                    }
                }
    
                const toolsInfo = toolsList.map(([name, tool]) => ({
                    name,
                    title: tool.title || name,
                    description: tool.description,
                    category: databaseTools.has(name) ? 'database' : 'metadata'
                }));
    
                return {
                    content: [{
                        type: 'text',
                        text: `Herramientas disponibles${args.category ? ` (categoría: ${args.category})` : ''}:\n\n${formatForClaude(toolsInfo)}`
                    }]
                };
            } catch (error) {
                logger.error('Error listing tools:', { error });
                return {
                    content: [{
                        type: 'text',
                        text: `Error listando herramientas: ${error instanceof Error ? error.message : String(error)}`
                    }],
                    isError: true
                };
            }
        }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic function without mentioning whether this is a read-only operation, if it requires authentication, what the output format looks like, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 unnecessary words. It's appropriately sized for a simple listing tool and front-loads the core functionality immediately.

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

Completeness2/5

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

Given the tool's simplicity (1 optional parameter, no output schema, no annotations), the description is minimal but adequate for basic understanding. However, it doesn't address important contextual aspects like what 'available' means in practice, whether tools are filtered by permissions, or how the output is structured. With no output schema and no annotations, more completeness would be helpful.

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?

The schema description coverage is 100%, with the single parameter 'category' fully documented in the schema. The description doesn't add any parameter information beyond what's already in the structured schema. Since schema coverage is high, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 action ('Lista todas las herramientas disponibles') and resource ('en el servidor MCP'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-tool-help' or 'list-tables', which might cause confusion about scope. The Spanish phrasing is clear but lacks explicit distinction from similar tools.

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 is provided on when to use this tool versus alternatives like 'get-tool-help' or other listing tools. The description simply states what it does without context about appropriate use cases, prerequisites, or comparisons to sibling tools that might serve similar discovery purposes.

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