Skip to main content
Glama

echo

Test connectivity and verify message transmission by returning input messages unchanged for validation purposes.

Instructions

Return the input message (for testing)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to echo back

Implementation Reference

  • src/index.ts:136-148 (registration)
    Registration of the 'echo' tool in the ListToolsRequestSchema handler.
      name: "echo",
      description: "Return the input message (for testing)",
      inputSchema: {
        type: "object",
        properties: {
          message: {
            type: "string",
            description: "Message to echo back",
          },
        },
        required: ["message"],
      },
    },
  • The handler logic for the 'echo' tool inside the CallToolRequestSchema handler.
    case "echo": {
      return {
        content: [
          {
            type: "text",
            text: `Echo: ${args.message}`,
          },
        ],
      };
    }
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 the input message, which is straightforward, but it doesn't disclose behavioral traits such as error handling, performance characteristics, or any constraints. For a tool with no annotations, this leaves gaps in understanding its behavior.

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 extremely concise and front-loaded, consisting of a single sentence that directly states the tool's function and purpose. Every word earns its place, with no unnecessary elaboration.

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 (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks depth in behavioral transparency and usage guidelines. For a simple testing tool, it's complete enough to understand the core function, but could be improved with more context.

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 'message' clearly documented. The description adds minimal value beyond the schema by implying the message is echoed back, but it doesn't provide additional semantic context like format examples or usage tips. Baseline 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 with a specific verb ('Return') and resource ('input message'), and it provides context about its testing function. However, it doesn't explicitly differentiate from sibling tools like 'compress' or 'decompress' beyond the basic 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 mentions 'for testing' which implies a context, but it doesn't provide explicit guidance on when to use this tool versus alternatives like the sibling tools. No when-not-to-use scenarios or specific alternatives are named.

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/loscolmebrothers/zip-mcp'

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