Skip to main content
Glama
igs-pochenkuo

SouthAsia MCP Tool

mcp_hello_world

Demonstrates how to create and integrate custom tools using the Model Control Protocol framework by returning a greeting message.

Instructions

A simple demonstration tool that returns a greeting message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYesDummy parameter for no-parameter tools

Implementation Reference

  • The handler logic for the 'mcp_hello_world' tool. It returns a TextContent object with a greeting message when the tool is called.
    if name == "mcp_hello_world":
        return [
            types.TextContent(
                type="text",
                text="Hello World! 這是您的第一個 mcp 工具!"
            )
        ]
  • The input schema for the 'mcp_hello_world' tool, defining a required dummy 'random_string' parameter.
    inputSchema={
        "type": "object",
        "properties": {
            "random_string": {
                "type": "string",
                "description": "Dummy parameter for no-parameter tools"
            }
        },
        "required": ["random_string"],
    },
  • The registration of the 'mcp_hello_world' tool object in the handle_list_tools function, which includes the name, description, and input schema.
    types.Tool(
        name="mcp_hello_world",
        description="A simple demonstration tool that returns a greeting message",
        inputSchema={
            "type": "object",
            "properties": {
                "random_string": {
                    "type": "string",
                    "description": "Dummy parameter for no-parameter tools"
                }
            },
            "required": ["random_string"],
        },
    ),
  • Registration of the hello_world handlers (including mcp_hello_world) in the HANDLERS list, matched by prefix 'mcp_hello'.
    HANDLERS = [
        {
            "prefixes": ["mcp_hello"],
            "list_tools": hello_world_list_tools,
            "call_tool": hello_world_call_tool
        }
    ]
  • Top-level registration of the combined list_tools and call_tool handlers on the MCP server instance.
    # 註冊工具列表處理器
    server.list_tools()(combined_list_tools)
    
    # 註冊工具調用處理器
    server.call_tool()(combined_call_tool)
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. It states the tool 'returns a greeting message', implying a read-only operation, but doesn't disclose any behavioral traits like error handling, rate limits, or authentication needs. For a tool with no annotation coverage, this is a significant gap in transparency.

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: 'A simple demonstration tool that returns a greeting message'. It is front-loaded with the core purpose and wastes no words, making it appropriately sized and easy to parse.

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 (one parameter with full schema coverage, no output schema), the description is adequate but has clear gaps. It explains the basic purpose but lacks usage guidelines and behavioral details, making it minimally viable but not fully complete for effective agent use.

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 input schema has 100% description coverage, with the parameter 'random_string' documented as a 'Dummy parameter for no-parameter tools'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting without extra value from the description.

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: 'returns a greeting message' with 'simple demonstration' providing context. It specifies the verb 'returns' and resource 'greeting message', making it understandable. However, it doesn't explicitly differentiate from its sibling 'mcp_hello_name', which appears similar, keeping it from 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. It mentions 'simple demonstration' but doesn't specify contexts, exclusions, or compare to 'mcp_hello_name'. This lack of usage instructions leaves the agent without clear direction for tool selection.

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/igs-pochenkuo/southasia_mcp'

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