Skip to main content
Glama

Agent Exchange store

util_echo

$0.001 via x402: Your query parameters and the request headers we saw (user-agent, accept, content-type), with the time; for testing a client's x402 flow. Pay 0.001 USDC through https://store.agentexchange.work/gw/util/echo?hello=world Via the Agent Exchange store gateway; settled by Coinbase.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "util_echo"
  }
}

Input Schema

NameRequiredDescriptionDefault
*No*
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose meaningful traits: the call costs 0.001 USDC via x402, payment flows through the Agent Exchange gateway, and settlement is by Coinbase. A caller learns this is a paid, payment-gated request rather than a free read. It does not cover rate limits or what happens on an unrejected/absent payment beyond what the schema implies, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a run-on: the price tag leads, then the function, then a raw example URL with a query string, then gateway and settlement notes. Leading with cost rather than the tool's function hurts front-loading, and the embedded full URL is low-value noise for an agent deciding whether to call the 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?

For a paid echo/test tool with no annotations and no output schema, the description covers the essentials: what it returns, that it costs money, and how payment is settled. The remaining gap – what is returned when no payment is supplied – is at least hinted at in the x_payment schema note, so the agent has enough to invoke it correctly.

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 '* ' wildcard and x_payment payload are already documented in the schema. The description reinforces that arbitrary query parameters are echoed but adds no syntax or format detail beyond what the schema provides. Baseline 3 for full schema coverage.

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 states concretely what comes back: the caller's query parameters, observed request headers (user-agent, accept, content-type), and the time. That distinguishes it from siblings like util_ping, util_time, and util_hash, which do not echo request headers. The verb is implicit ('echoes/returns') rather than explicit, but the resource and payload are unambiguous.

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

Usage Guidelines3/5

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

It gives one clear context: 'for testing a client's x402 flow.' That implies when to reach for this tool, but there are no exclusions, prerequisites, or comparison to alternatives such as util_ping or util_status. Usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources