Skip to main content
Glama
MCP Server Boilerplate

MCP Server Boilerplate

by jeandbonicel

Echo

echo
Read-only

Returns the supplied message unchanged to verify connectivity between a client and the MCP server. Use it to test that requests and responses work correctly.

Instructions

Echoes back the provided message. Useful for testing connectivity.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. The description adds that the operation is a pure round-trip of the input, which is useful context, but it does not describe the response shape, any size limits, or whether the message is transformed. Against the lower bar set by annotations, this is adequate but thin.

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?

Two short sentences with zero filler: the behavior comes first, then the use case. Every sentence earns its place and nothing is buried.

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 one-parameter, non-destructive round-trip utility with full schema coverage and no output schema, the description covers everything an agent needs to call it correctly. No permissions, side effects, or edge cases exist that would require further disclosure.

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% with a single required string parameter that is self-documenting. The description restates the parameter implicitly ("the provided message") without adding constraints such as length or encoding. Baseline 3 is appropriate since the schema does the work.

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?

"Echoes back the provided message" names a specific verb and resource, and the tool is clearly distinguishable from the listed siblings (calculator, database, fetch-api, file-ops). It stops short of saying whether the return value is the raw string or a wrapped payload, so it is clear but not maximally precise.

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?

"Useful for testing connectivity" gives an explicit use case, which is exactly what an agent needs for a trivial utility tool. There are no stated exclusions or named alternatives, but for a tool with no behavioral overlap with its siblings, that omission is minor.

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