Skip to main content
Glama

x420_spend_summary

Read-only

Returns paid-call totals, rolling 24h and lifetime spend, remaining per-call, daily, and lifetime caps, plus wallet status and the verified seller pay-to address for this server.

Instructions

Free. This server's own spending so far: paid calls, total USD, last-24h USD, the caps (X420_MCP_MAX_USD per call, X420_MCP_MAX_TOTAL_USD lifetime, X420_MCP_MAX_DAILY_USD rolling 24h) and what remains under each, plus whether a wallet is configured and the verified seller pay-to address.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description adds substantial context beyond them: that invocation is free, the exact cap semantics (per-call X420_MCP_MAX_USD, lifetime X420_MCP_MAX_TOTAL_USD, rolling-24h X420_MCP_MAX_DAILY_USD), and that wallet configuration and the verified seller pay-to address are reported. It does not describe whether the numbers reflect in-flight calls or include failed requests, so a small gap remains.

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?

A single dense sentence with the most decision-relevant fact ('Free.') front-loaded, followed by the returned fields and cap definitions. It is compressed rather than padded, though the long parenthetical of env-var names makes it slightly harder to scan than a short bulleted enumeration would be.

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 parameters and no output schema, the description must carry the return-value burden and largely does, naming each reported figure and how each cap is scoped. An agent knows what it will get back and that the call costs nothing. The only omissions are edge details such as rounding, currency, and whether the summary includes the current call itself.

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?

There are zero parameters, so there is nothing to disambiguate and the baseline is 4. The environment-variable names mentioned are configuration surfaced in the result, not inputs, so they do not create confusion about how to call the tool.

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 plainly that this reports 'this server's own spending so far' and enumerates the returned fields (paid calls, total USD, last-24h USD, caps, remaining allowance, wallet status, seller pay-to address). That makes the resource and its content unambiguous. It stops short of a crisp verb-first phrasing and doesn't explicitly differentiate from any sibling, though no sibling in the catalog overlaps this cost-accounting function.

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?

'Free.' gives a clear signal that calling it has no cost, which is useful context an agent would otherwise have to infer. Beyond that there is no explicit when-to-use or when-not-to-use guidance and no named alternative. For a zero-parameter self-introspection tool this is largely implied, but the placement is implicit rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.