Skip to main content
Glama
ilil1

Simple MCP Server

by ilil1

hello_world

Generate greeting messages by specifying a name and optional delay. Returns personalized responses for testing or demonstration purposes.

Instructions

A simple hello world tool that returns a greeting.

    Args:
        name: Name to greet
        delay: Optional delay in seconds

    Returns:
        A greeting message
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoWorld
delayNo

Implementation Reference

  • run_server.py:61-61 (registration)
    Registration of the 'hello_world' tool using the @mcp.tool() decorator on the FastMCP instance.
    @mcp.tool()
  • The implementation of the 'hello_world' tool handler. It logs the call, sleeps if delay specified, and returns a greeting message.
    async def hello_world(name: str = "World", delay: int = 0) -> dict:
        """A simple hello world tool that returns a greeting.
    
        Args:
            name: Name to greet
            delay: Optional delay in seconds
    
        Returns:
            A greeting message
        """
        logger.info(f"hello_world called with name={name}, delay={delay}")
        if delay > 0:
            await asyncio.sleep(delay)
        return {"message": f"Hello, {name}!"}
Behavior2/5

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

With no annotations provided, the description carries the full burden. It mentions the tool returns a greeting and has an optional delay, but lacks details on behavioral traits such as whether it's read-only, if it has side effects, rate limits, or error handling. The description doesn't contradict annotations (none exist), but it's insufficient for a tool with parameters.

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

Conciseness4/5

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

The description is appropriately sized with a brief overview and structured parameter/return sections. It's front-loaded with the purpose, but the formatting with indentation and bullet-like points could be more streamlined for clarity.

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 low complexity (2 parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It explains parameters and returns, but lacks behavioral context and usage guidelines. For a simple tool, it's adequate but not fully comprehensive.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'name' is for greeting and 'delay' is an optional delay in seconds, which clarifies beyond the schema's basic titles. However, it doesn't cover defaults (e.g., name defaults to 'World') or constraints, leaving some gaps.

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

Purpose3/5

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

The description states the tool returns a greeting, which is a clear purpose, but it's vague about what 'hello world' entails beyond that. It doesn't distinguish from siblings like get_version or system_info, which might also return simple outputs. The phrase 'simple hello world tool' is somewhat tautological with the name.

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_version or system_info. The description implies it's for greetings, but there's no explicit context for when it's appropriate or any exclusions mentioned.

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/ilil1/simple-mcp-server'

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