Skip to main content
Glama

Platform Statistics

platform_stats
Read-onlyIdempotent

Live 402Proof platform statistics: total settled payments, settled volume, and active agent count across the XRPL, Xahau, Base, and Solana rails. Read-only. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds two pieces of genuine value beyond that: 'Live' signals freshness/real-time data and 'Free' signals no cost or quota, but it says nothing about refresh cadence, caching, or rate limits.

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?

The metric list is front-loaded and every content sentence earns its place. The trailing 'Read-only.' fragment largely restates the readOnlyHint annotation, making it the one redundant element in an otherwise tight definition.

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?

With no input parameters and no output schema, the description must carry the burden of telling the agent what comes back, and it does so by naming the three metrics and the four chains. It stops short of specifying units, currencies, or how the figures are aggregated, which leaves some ambiguity for a statistics endpoint.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. Nothing in the description misleads about inputs.

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 gives a specific resource (402Proof platform statistics) and enumerates exactly what is returned: total settled payments, settled volume, and active agent count, scoped to XRPL, Xahau, Base, and Solana. It is clearly distinguishable from the attestation/verification siblings, though it never explicitly names an alternative.

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?

Usage is only implied: an agent can infer this is the tool for platform-wide aggregate numbers rather than per-payment or per-agent data. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for a different question, and no mention of prerequisites.

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