Skip to main content
Glama
Sign In
ChillMCP

ChillMCP

by DreamFriend011020
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Echo Tool

echo

Send a message and receive it back unchanged to test connectivity and confirm the server is responsive.

Instructions

Echoes back the provided 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
messageYesThe message to echo back

Output Schema

NameRequiredDescriptionDefault
echoYes
timestampYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it fully discloses the behavior: the tool simply echoes back the provided message. There are no side effects, permissions, or hidden behaviors to disclose, and the output schema covers the return format.

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 a single, front-loaded sentence with zero wasted words. It is optimally concise for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial one-parameter tool with an output schema, the description is completely sufficient. An agent can invoke the tool correctly without any missing information.

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?

Schema description coverage is 100%, so the parameter 'message' is already fully documented in the schema. The description adds no additional parameter semantics, which fits the baseline for high schema coverage.

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

Purpose5/5

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

The description 'Echoes back the provided message' uses a specific verb and resource, and clearly distinguishes this tool from siblings like add, multiply, calculate, and get-time. There is no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies the tool is for echoing a message back, and none of the sibling tools offer this functionality, so the context is clear. However, there is no explicit statement about when to use it versus alternatives, though the alternatives are obviously unrelated.

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