Skip to main content
Glama

APEX x402 & AI Agent Tools (360 tools)

Faucet metrics

faucet_metrics

The X1 APEX faucet's own record: claims, APEX and XNT paid out, and unique wallets, for the last 24 h, 7 days, 30 days and all time. Free. For the Arc USDC faucet use arc_faucet_status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 disclosure burden; it does note the operation is free and implies a passive read of a 'record'. It does not state rate limits, freshness/latency of the aggregates, or whether figures are cumulative or per-period, which matters for a metrics endpoint with four time windows.

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

Conciseness5/5

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

Two sentences, both earning their place: the first front-loads the resource and its contents plus the time windows, the second handles cost and sibling disambiguation. No filler or restatement of the title.

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 output schema and no parameters, the description effectively serves as the return-value specification by listing the metric families (claims, APEX and XNT paid out, unique wallets) and the four aggregation windows. Only the response shape (per-window object vs. flat list) remains unstated, a minor gap for a stats 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 nothing for the description to disambiguate at the input layer. Baseline for a parameterless tool is 4, and the description adds nothing that conflicts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource ('the X1 APEX faucet's own record') and enumerates exactly what the record contains: claims, APEX and XNT paid out, and unique wallets. It also names a sibling (arc_faucet_status) that covers a different faucet, so the agent can distinguish the two without opening either schema.

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?

It gives explicit routing guidance away from this tool ('For the Arc USDC faucet use arc_faucet_status'), which is the main selection ambiguity given a large sibling list. It lacks explicit when-to-use framing (e.g. monitoring payout volume vs. checking claim eligibility), but for a metrics-only tool the context is clear.

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.