Skip to main content
Glama

Chain status

chain_status

Live X1 blockchain health, TPS, validators, slot lag, and RPC status. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "chain_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does disclose the crucial behavior that an unpaid call returns terms rather than data, plus the per-call price and accepted payment rails, which is valuable and non-obvious. It stops short of stating whether the first call is free, whether payments are single-use or expire, or what happens on payment failure.

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?

Two sentences, front-loaded with what the tool returns before the commercial mechanics. Dense but every clause carries information; only the currency list is slightly cluttered.

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?

Adequate for a one-parameter status endpoint with no output schema: known metrics, known price, known payment flow. Gaps remain around failure modes and payment reuse, which matter for a paid tool where an agent could waste a transaction.

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

Parameters4/5

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

Schema coverage is 100% and the single `payment` parameter is already well documented, so baseline is 3. The description earns an extra point by explaining the lifecycle the parameter participates in (unpaid call yields terms, signed base64 payload completes the purchase in-call).

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 resource (live X1 chain health) and enumerates the exact metrics returned: TPS, validators, slot lag, RPC status. No sibling differentiation is offered, so an agent cannot tell from the description alone why it would pick this over arc_rpc_status or arc_agent_status.

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

Usage Guidelines4/5

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

Gives an explicit two-step invocation recipe: call without `payment` to receive terms, sign with your own wallet, call again with `payment`. That is clear procedural guidance, but there is no guidance on when this tool is preferred over the many sibling status/quote tools.

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