Skip to main content
Glama
Sign In
MCP Tool Server

MCP Tool Server

by nuvolalabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

echo

Returns the supplied message unchanged to verify input handling and confirm tool communication.

Instructions

Echo back a message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "echo"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it omits the one behavioral fact that matters here: whether the return is the message verbatim, wrapped in an object, or accompanied by metadata. Nothing about idempotency, side effects, or response shape is disclosed.

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?

One short, front-loaded sentence with no waste. Appropriately sized for a trivial utility, though it errs toward under-specification rather than economy.

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?

The tool is simple enough that an agent can call it correctly, but without an output schema the description should say what comes back. That gap is the only real omission for a one-parameter passthrough.

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?

Schema coverage is 0% and the single parameter has no description in the schema. The description's phrase "a message" adds no meaning beyond the parameter name 'message' — no format, length, or encoding constraints.

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?

"Echo back a message" names a verb and a resource, so the agent can tell it is a passthrough utility, but it is essentially a restatement of the tool name 'echo'. It is distinguishable from siblings (add, sqrt, now_utc) only by virtue of those being unrelated, not by anything the description says.

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 when-to-use, when-not-to-use, or alternative is mentioned. The tool's role is guessable but the description provides zero routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools