Skip to main content
Glama
hanweg

mcp-tool-builder

by hanweg

list_available_tools

Discover all tools currently accessible in the MCP tool builder server to understand available functionality and capabilities.

Instructions

List all currently available tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for executing the 'list_available_tools' tool. It iterates over self.tools_config to create a formatted list of available tools and returns it as text content.
    elif name == "list_available_tools":
        tools_list = "\n".join([
            f"- {tool['name']}: {tool.get('description', 'No description')}"
            for tool in self.tools_config
        ])
        return [types.TextContent(
            type="text",
            text=f"Available tools:\n{tools_list}"
        )]
  • Registration of the 'list_available_tools' tool within the handle_list_tools function. Defines the tool name, description, and empty input schema.
    types.Tool(
        name="list_available_tools",
        description="List all currently available tools",
        inputSchema={
            "type": "object",
            "properties": {},
            "required": []
        }
    ),
  • Input schema for the 'list_available_tools' tool, which requires no parameters.
    inputSchema={
        "type": "object",
        "properties": {},
        "required": []
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without disclosing behavioral traits like whether it's read-only, requires authentication, has rate limits, or what format the output takes. It's minimal and lacks essential context for a tool that lists resources.

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 with no wasted words, front-loading the core purpose. It's appropriately sized for a simple tool and earns its place by clearly stating the action.

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 (0 parameters, no output schema), the description is incomplete. It lacks context on output format, behavioral aspects like safety or permissions, and doesn't leverage the opportunity to guide usage relative to siblings, making it inadequate for full agent understanding.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and its mention of 'all currently available tools' implies no filtering, which aligns with the empty schema. Baseline is 4 for zero parameters.

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 ('List') and resource ('all currently available tools'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'create_tool' which has a different purpose, so it falls short of a perfect score.

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 'create_tool' for creating tools or other unrelated siblings. There's no mention of context, prerequisites, or exclusions, leaving usage entirely implicit.

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/hanweg/mcp-tool-builder'

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