zero-core-budget

report_spend

Record a completed spend with optional outcome tracking. Call this AFTER paying for a service to track spending and build ROI history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "service_id": "<service_id>",
      "amount_usd": "<amount_usd>",
      "category": "<category>"
    },
    "name": "report_spend"
  }
}

Input Schema

Name	Required	Description
`agent_id`	Yes	Your agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it
`category`	Yes	Spending category
`amount_usd`	Yes	Amount spent in USD
`service_id`	Yes	Service that was used
`value_received`	No	Description of value received
`outcome_success`	No	Whether the service call succeeded

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Your agent identifier"New value: +"Your agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it"

First observedApr 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a write operation and clarifies that it records rather than performs payment ('AFTER paying'), but it does not disclose effects on wallet balance, idempotency or duplicate handling, permissions beyond the schema's wallet note, or error behavior. Significant gaps remain for a mutation tool.

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 with zero waste. The action and the timing constraint are front-loaded and immediately actionable.

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?

With six parameters, no annotations, and no output schema, the description should say more about what happens on the write and what the caller gets back. The core action and timing are covered, but mutation effects and return behavior are absent.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters including the enum and wallet ownership constraint. The description only hints at 'optional outcome tracking', mapping loosely to outcome_success and value_received; baseline 3 is appropriate when the schema does the heavy lifting.

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 a specific verb and resource: 'Record a completed spend' with 'optional outcome tracking'. An agent can tell this apart from the read-oriented siblings (check_spend, get_spending_report), though it does not name them explicitly.

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 clear timing and context: 'Call this AFTER paying for a service to track spending and build ROI history.' This establishes when to invoke it. However, it does not name alternatives or exclusions (e.g., use check_spend for lookups) explicitly.

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

All zero-core-budget tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.