Skip to main content
Glama
Sign In

zero-core-budget

by io.github.meltingpixelsai
OverviewDiscussionsAdmin

get_spending_report

Detailed spending analytics report. Returns total spent, category breakdown, top services with ROI, and optimization recommendations. Use to understand spending patterns and find inefficiencies.

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>",
      "period": "<period>"
    },
    "name": "get_spending_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYesReport period
agent_idYesYour agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return contents (totals, category breakdown, top services with ROI, recommendations). It still omits permission requirements, whether the operation is strictly read-only, and any rate or error behavior, leaving meaningful gaps for a no-annotation 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?

It is three focused sentences: purpose first, returned fields second, usage third. Nothing is redundant, and the key information is front-loaded.

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?

For a two-parameter read-only analytics tool with a fully documented schema, the description is mostly complete and importantly lists return values since no output schema exists. It could still be stronger by clarifying how it differs from check_spend and by stating its read-only nature explicitly.

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 both the period enum and agent_id wallet constraint are already documented in the schema. The description adds no additional parameter semantics, making the baseline 3 appropriate.

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 clearly states a specific resource, a detailed spending analytics report, and lists the outputs it returns. It does not explicitly differentiate this tool from the sibling check_spend, so it falls short of a 5.

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 a clear usage context: 'Use to understand spending patterns and find inefficiencies.' However, it does not state when not to use it or name alternatives such as check_spend, so it lacks the explicit alternative routing that would merit a 5.

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 toolsInspect
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.

Resources