Skip to main content
Glama
currentspace

Bootstrap MCP Server

by currentspace

echo

Test MCP server functionality by returning provided messages, enabling developers to verify communication and validate tool integration in the Bootstrap MCP Server.

Instructions

Echo back the provided message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage to echo

Implementation Reference

  • The handler function that implements the 'echo' tool logic. It extracts the 'message' from the input arguments and returns it as a text content response.
    private handleEcho(args: any) {
        const message = args.message as string
        return {
            content: [
                {
                    type: 'text',
                    text: message,
                },
            ],
        }
    }
  • The schema definition for the 'echo' tool, including name, description, and input schema specifying a required 'message' string.
    {
        name: 'echo',
        description: 'Echo back the provided message',
        inputSchema: {
            type: 'object',
            properties: {
                message: {
                    type: 'string',
                    description: 'Message to echo',
                },
            },
            required: ['message'],
        },
    },
  • src/server.ts:84-85 (registration)
    The switch case in the tool execution handler that registers and dispatches the 'echo' tool call to its handler function.
    case 'echo':
        return this.handleEcho(args)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the echo action but doesn't mention any behavioral traits like whether it modifies input, has rate limits, requires authentication, or what format the output takes. 'Echo back' implies a simple return, but no details are given about the return mechanism or potential side effects.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the core functionality immediately.

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?

For a simple 1-parameter tool with no annotations and no output schema, the description is minimally adequate. It states the basic purpose but lacks details about output format or behavioral context that would be helpful given the absence of structured fields. It's complete enough to understand what it does but not rich in operational guidance.

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 parameter 'message' fully documented in the schema as 'Message to echo'. The description doesn't add any meaning beyond what the schema provides about parameters, so it meets the baseline of 3 when the schema does the heavy lifting.

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 ('Echo back') with the specific resource ('the provided message'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'get_time' or 'hello_world', but the verb+resource combination is specific enough for basic understanding.

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 guidance is provided about when to use this tool versus alternatives like 'hello_world' (which might return a fixed greeting) or 'get_time' (which returns time data). The description only states what it does, not when it should be selected over sibling 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/currentspace/bootstrap_mcp'

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