Skip to main content
Glama

my_tool

Extend AI application functionality in Claude Desktop using modular tools without modifying core code. Configure custom parameters to add specific capabilities.

Instructions

自定义工具

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramYes

Implementation Reference

  • The handler implementation for the 'my_tool' tool, decorated with @server.tool() which also handles registration. It takes a string parameter and returns a formatted processing message.
    @server.tool()
    def my_tool(param: str) -> str:
        """自定义工具"""
        return f"处理参数: {param}"
  • The @server.tool() decorator registers the my_tool function in the module's register method.
    @server.tool()
  • The function signature defines the input schema (param: str) and output type (str) for the my_tool.
    def my_tool(param: str) -> str:
Behavior1/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 but fails completely. '自定义工具' gives no indication of whether this is a read/write operation, its side effects, permissions needed, or any behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just three characters, this is under-specification rather than effective brevity. The description fails to convey necessary information, making it inefficient despite its short length.

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

Completeness1/5

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

For a tool with one undocumented parameter, no annotations, and no output schema, the description is completely inadequate. It provides no functional context, parameter guidance, or behavioral information needed for proper tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no information about the single required parameter 'param'. It doesn't explain what 'param' represents, its format, or how it influences the tool's behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '自定义工具' (custom tool) is a tautology that merely restates the tool name 'my_tool' without specifying what it actually does. It provides no verb, resource, or functional purpose, and doesn't distinguish it from sibling tools like 'add', 'hello', or 'server_info'.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. There's no mention of context, prerequisites, or comparisons with sibling tools, leaving the agent with no usage direction.

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/gooboot/MCP-BOS'

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