Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-rpc-health

RPC Health: Checks up to 10 JSON-RPC endpoints with an RPC call and reports which answer 🆓 5 free trial calls per signed wallet

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": "x402-rpc-health"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpcsNo
urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / rpcs / description
      Removed value: -"Rpcs to process"
    • removedInput schema / properties / urls / description
      Removed value: -"Urls to process"
  2. First observed

TDQS

C2.7/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 burden. It discloses the 10-endpoint cap and per-wallet free-call quota, but says nothing about read-only safety, authentication/signing requirements, timeouts, or how failures are reported. The payment hint is useful but behavioral coverage is thin for an unannotated tool.

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 compact sentence, front-loaded with the operation and the resource. The emoji and promo clause dilute it slightly but it remains tight and readable.

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

Completeness2/5

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

No annotations, no output schema, two fully undocumented parameters, and no description of the result shape beyond 'which answer'. For a network-probing tool whose chief risks (timeout, auth, partial results) matter to callers, this is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never disambiguates the two string parameters (rpcs vs urls), which are the crux of the tool's input. 'JSON-RPC endpoints' is a vague hint at best; the caller must guess the format and the role of each parameter.

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 (checks) and resource (JSON-RPC endpoints) plus a concrete scope limit (up to 10) and output intent (reports which answer). It does not differentiate itself from near-siblings like x402-rpc, x402-ping-check, or x402-liveness-check-v1, so it stops short of a 5.

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, and no named alternative among the many uptime/ping/RPC siblings. The only contextual note is the free-trial quota, which is pricing rather than usage direction.

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.