Skip to main content
Glama

Agent Exchange store

util_status

$0.001 via x402: Health of this host and of the store (reachable, status code, latency in ms) with the time. Pay 0.001 USDC through https://store.agentexchange.work/gw/util/status 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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that this is a paid x402 tool ($0.001 USDC), routed via the Agent Exchange store gateway and settled by Coinbase, and it lists the returned fields. However, it omits rate limits, per-call vs session payment semantics, and failure behavior.

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 purpose and price are front-loaded, which is good, but payment details are stated redundantly ('$0.001 via x402', 'Pay 0.001 USDC', repeated gateway URL) and the run-on structure mixes purpose, price, and infrastructure into one dense block.

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 single-parameter status tool with no annotations and no output schema, the description is largely complete: it names the returned fields (reachable, status code, latency, time) and explains the payment model. Only edge-case and error behavior are unaddressed.

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?

There is a single parameter (x_payment) with 100% schema description coverage, so the schema already explains it as an optional signed payload. The description only reinforces that payment is the operative concept and adds no syntax or format detail beyond the schema, matching the baseline of 3.

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 a specific resource: the health of the host and of the store, with enumerated outputs (reachable, status code, latency in ms, time). This distinguishes it reasonably from generic siblings, though the intended verb is only implied and somewhat buried between payment clauses.

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?

There is no guidance on when to use this versus alternatives such as util_ping or util_time. The only contextual constraint mentioned is the payment requirement, which is a prerequisite rather than usage guidance or an alternative-selection rule.

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