Skip to main content
Glama
109naoki

minimal-mcp-server

by 109naoki
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

echo

Returns the exact message you input, enabling message verification and testing in the minimal-mcp-server environment.

Instructions

入力されたメッセージをそのまま返す簡単なツール

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesエコーするメッセージ

Implementation Reference

  • src/index.ts:12-19 (registration)
    Registration of the "echo" tool.
    server.registerTool(
  "echo",
  {
    description: "入力されたメッセージをそのまま返す簡単なツール",
    inputSchema: {
      message: z.string().describe("エコーするメッセージ"),
    },
  },
  • src/index.ts:20-29 (handler)
    Handler implementation for the "echo" tool.
    async ({ message }) => {
  return {
    content: [
      {
        type: "text",
        text: `Echo: ${message}`,
      },
    ],
  };
},

Tool Definition Quality

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the message is returned 'as-is' (そのまま), indicating an identity function behavior, but lacks disclosure of side effects, idempotency, synchronous/asynchronous nature, or error conditions.

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, efficiently structured sentence that immediately communicates the core functionality. There is no redundant information or unnecessary elaboration for this simple utility tool.

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

Completeness4/5

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

Given the tool's simplicity (single string input, identity transformation), 100% schema coverage, and the universal understanding of 'echo' functionality, the description is reasonably complete. While an output schema is absent, the description adequately covers the input-to-output relationship for this trivial operation.

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 the single parameter 'message' fully documented in the schema as 'エコーするメッセージ'. The description implies the message will be returned but does not add syntax details, constraints, or examples beyond the schema definition, warranting the baseline score.

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 clearly states the tool 'returns the input message as-is' (入力されたメッセージをそのまま返す), using a specific verb and resource. It clearly distinguishes from siblings get-current-time and search-wikipedia, as echoing messages is functionally distinct from retrieving time or searching encyclopedia entries.

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. While the purpose is obvious from the name and description, there is no explicit guidance on preferred use cases (e.g., testing connectivity, debugging) or when to avoid it in favor of more complex messaging 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/109naoki/minimal-mcp-server'

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