Skip to main content
Glama
igs-pochenkuo

SouthAsia MCP Tool

mcp_hello_name

Generate personalized greetings by entering your name. This tool creates custom welcome messages for users interacting with the MCP framework.

Instructions

A demonstration tool that greets you by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesYour name

Implementation Reference

  • The core handler logic for the 'mcp_hello_name' tool. It extracts the user's name from the arguments, validates its presence, and returns a personalized greeting message as TextContent.
    elif name == "mcp_hello_name":
        user_name = arguments.get("name")
        if not user_name:
            raise ValueError("缺少名字參數")
            
        return [
            types.TextContent(
                type="text",
                text=f"Hello {user_name}! 很高興見到您!"
            )
        ]
  • The JSON schema definition for the 'mcp_hello_name' tool, specifying the required 'name' string parameter.
    types.Tool(
        name="mcp_hello_name",
        description="A demonstration tool that greets you by name",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "Your name"
                }
            },
            "required": ["name"],
        },
    ),
  • Registration of the hello_world handler module in the HANDLERS list using prefix 'mcp_hello', which routes tool calls for 'mcp_hello_name' to the appropriate list_tools and call_tool functions in hello_world.py.
    HANDLERS = [
        {
            "prefixes": ["mcp_hello"],
            "list_tools": hello_world_list_tools,
            "call_tool": hello_world_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 full burden. It states the tool 'greets you by name' but doesn't disclose behavioral traits like whether this is a read-only operation, what format the greeting returns, if there are any side effects, or authentication requirements. The description is minimal and lacks behavioral context.

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 clearly states the tool's purpose. It's appropriately sized for a simple greeting tool with one parameter. Every word earns its place with zero waste or redundancy.

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?

For a simple greeting tool with one parameter and no output schema, the description is adequate but has clear gaps. It explains what the tool does but doesn't provide usage context, behavioral details, or output information. Given the tool's simplicity, the description meets minimum viable standards but could be more complete.

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?

Schema description coverage is 100% with the single parameter 'name' well-documented as 'Your name'. The description adds no additional parameter semantics beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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: 'greets you by name' specifies the action (greeting) and resource (name). It distinguishes from sibling 'mcp_hello_world' by specifying personalized greeting vs generic greeting. However, it doesn't explicitly mention the sibling differentiation in the description text itself.

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. There's no mention of sibling tool 'mcp_hello_world' or any context about when a personalized greeting is preferred over a generic one. The description simply states what it does without usage context.

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