Skip to main content
Glama

echo

Send messages to receive identical responses for testing communication protocols or verifying message transmission in MCP server environments.

Instructions

Echo back the input message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to echo back

Implementation Reference

  • server.js:84-92 (handler)
    Handler for the 'echo' tool that echoes back the input message prefixed with 'Echo: ' in a text content block.
    case 'echo':
      return {
        content: [
          {
            type: 'text',
            text: `Echo: ${args.message}`,
          },
        ],
      };
  • Input schema for the 'echo' tool, requiring a 'message' string.
    inputSchema: {
      type: 'object',
      properties: {
        message: {
          type: 'string',
          description: 'Message to echo back',
        },
      },
      required: ['message'],
    },
  • server.js:30-43 (registration)
    Registration of the 'echo' tool in the ListTools response, including name, description, and input schema.
    {
      name: 'echo',
      description: 'Echo back the input message',
      inputSchema: {
        type: 'object',
        properties: {
          message: {
            type: 'string',
            description: 'Message to echo back',
          },
        },
        required: ['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 of behavioral disclosure. It states the tool 'echoes back' the input, implying a read-only or non-destructive operation, but it doesn't disclose any behavioral traits such as side effects, error handling, or output format. This leaves gaps in understanding how the tool behaves beyond its basic function.

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 with 'Echo back the input message', a single sentence that directly conveys the tool's purpose without any wasted words. It's appropriately sized for a simple tool with one parameter.

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, no annotations, no output schema), the description is minimally complete. It states what the tool does but lacks details on usage guidelines, behavioral traits, or output, which could be helpful for an AI agent. However, for such a basic tool, it's adequate but leaves room for improvement in 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' documented as 'Message to echo back'. The description adds no additional meaning beyond this, as it only repeats the concept of echoing back a message without providing extra context or semantics. This meets the baseline of 3 since the schema adequately covers the parameter.

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 function as 'Echo back the input message', which specifies the verb ('echo back') and resource ('input message'). It's not tautological with the name 'echo' since it adds 'back the input message', but it doesn't differentiate from siblings like 'calculate' or 'get_system_info', which are unrelated tools.

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 doesn't mention any specific contexts, prerequisites, or exclusions, and with siblings like 'calculate' and 'get_system_info', there's no indication of when 'echo' is the appropriate choice over those tools.

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/balajidommeti/MCP'

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