Skip to main content
Glama
MCP Echo Service

MCP Echo Service

Echo Json

echo_json

Use echo_json to echo back structured JSON data with built-in validation and analysis, verifying payload integrity and inspecting JSON responses for MCP protocol testing.

Instructions

Echo back structured JSON data with validation and analysis.

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": {
      "data": "<data>"
    },
    "name": "echo_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe JSON data to echo back

Output Schema

NameRequiredDescriptionDefault
analysisYesAnalysis of the data structure
timestampYesISO 8601 timestamp of the operation
echoed_dataYesThe echoed JSON data
original_dataYesThe original JSON data sent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / data / description
      Added value: +"The JSON data to echo back"
    • removedOutput schema / $defs
      Removed value: -{
      -  "DataAnalysis": {
      -    "description": "Analysis metadata for JSON data.",
      -    "properties": {
      -      "data_types": {
      -        "additionalProperties": {
      -          "type": "string"
      -        },
      -        "description": "Mapping of keys to their data types",
      -        "type": "object"
      -      },
      -      "key_count": {
      -        "description": "Number of keys in the data",
      -        "type": "integer"
      -      },
      -      "keys": {
      -        "description": "List of all keys in the data",
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "total_size": {
      -        "description": "Total size of the JSON data in bytes",
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "key_count",
      -      "keys",
      -      "data_types",
      -      "total_size"
      -    ],
      -    "type": "object"
      -  }
      -}
    • removedOutput schema / properties / analysis / $ref
      Removed value: -"#/$defs/DataAnalysis"
    • addedOutput schema / properties / analysis / properties
      Added value: +{
      +  "data_types": {
      +    "additionalProperties": {
      +      "type": "string"
      +    },
      +    "description": "Mapping of keys to their data types",
      +    "type": "object"
      +  },
      +  "key_count": {
      +    "description": "Number of keys in the data",
      +    "type": "integer"
      +  },
      +  "keys": {
      +    "description": "List of all keys in the data",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "total_size": {
      +    "description": "Total size of the JSON data in bytes",
      +    "type": "integer"
      +  }
      +}
    • addedOutput schema / properties / analysis / required
      Added value: +[
      +  "key_count",
      +  "keys",
      +  "data_types",
      +  "total_size"
      +]
    • addedOutput schema / properties / analysis / type
      Added value: +"object"
  2. Addedv0.1.8
  3. Removedv0.1.7
  4. First observedv0.1.5

TDQS

C2.9/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 behavioral burden, yet it only asserts 'validation and analysis' without saying what validation rules apply or what analysis is performed. Since the output schema exists, return format is partly covered, but the promised side behaviors remain unexplained.

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 sentence, front-loaded with the core action, with no padding. The trailing 'validation and analysis' phrase is close to filler since neither is elaborated.

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?

An output schema exists, so return values need not be explained, and the single input is fully documented. The gap is that the advertised validation and analysis behavior is left opaque, which an agent may need in order to trust the echoed result.

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 coverage is 100% and the single 'data' parameter is documented as the JSON object to echo, so the schema does the work. The description adds no meaning beyond that, matching the baseline of 3 for a fully documented schema.

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?

States a specific verb and resource (echo back structured JSON data), which is enough for an agent to know the basic operation. However it does not differentiate itself from the sibling echo_message, leaving the message-vs-JSON distinction implicit.

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 or when-not-to-use guidance is given, and no alternative is named despite there being two closely related siblings (echo_message, echo_with_delay). The agent must guess which echo variant fits.

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