Skip to main content
Glama
piebro

Echo MCP Server

by piebro
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

echo_tool

Test MCP clients by sending messages and receiving identical responses to verify communication protocols.

Instructions

Echo a message as a tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes

Implementation Reference

  • echo_mcp_server_for_testing/main.py:9-13 (handler)
    The main handler function for the echo_tool that processes the input message, logs info, retrieves SECRET_KEY from environment, and returns the echoed response.
    async def echo_tool(message: str, ctx: Context) -> str:
    """Echo a message as a tool"""
    SECRET_KEY = os.getenv("SECRET_KEY", "No secret key found")
    await ctx.info(f"Processing echo request for message: '{message}'")
    return f"Tool echo: {message}. The environment variable SECRET_KEY is: {SECRET_KEY}"
  • echo_mcp_server_for_testing/main.py:8-8 (registration)
    The @mcp.tool() decorator that registers the echo_tool with the MCP server.
    @mcp.tool()

Tool Definition Quality

C2.2/5.0
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 of behavioral disclosure. The description only states 'Echo a message as a tool' which reveals nothing about what the tool actually does behaviorally - whether it's a read operation, a transformation, a test utility, or something else. It doesn't mention any side effects, permissions needed, rate limits, or what 'echo' means in practical terms.

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 extremely concise at just 5 words, which is appropriate for a simple tool. There's no wasted language or unnecessary elaboration. However, this conciseness comes at the cost of meaningful content - it's brief but under-specified rather than efficiently informative.

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?

For a tool with 1 parameter, no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what the tool does, how to use it, what the parameter means, or what to expect as output. The description fails to provide the minimal context needed for an agent to understand and use this tool effectively.

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

Parameters2/5

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

The schema has 1 parameter with 0% description coverage, meaning the schema provides no semantic information about the 'message' parameter. The description doesn't mention parameters at all, offering no compensation for the schema's lack of documentation. The description should explain what kind of message is expected or what the parameter represents, but it remains completely silent on this.

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

Purpose2/5

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

The description 'Echo a message as a tool' is a tautology that essentially restates the tool name 'echo_tool' without adding meaningful specificity. It uses the verb 'echo' which matches the name, but doesn't explain what 'echo' means in this context or what resource is being acted upon. No sibling tools exist to differentiate from, but the description remains vague about the actual function.

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, what scenarios it's designed for, or any prerequisites. With no sibling tools, there's no need to differentiate from alternatives, but the description doesn't indicate any context for usage. It's a minimal statement that offers no practical guidance to an agent.

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/piebro/echo-mcp-server-for-testing'

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