Skip to main content
Glama
Sign In

zero-core-budget

by io.github.meltingpixelsai
OverviewDiscussionsAdmin

check_spend

Pre-spend budget approval check. Verifies daily/weekly/category limits, estimates ROI from your own past spends with this service, and suggests cheaper alternatives you have used. Call this BEFORE paying for any service.

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

Input Schema

NameRequiredDescriptionDefault
agent_idYesYour agent's name. It belongs to the wallet you pay from: only calls paid from that wallet can read or change it (register it first)
categoryYesSpending category
amount_usdYesAmount you're about to spend in USD
service_idYesService you want to pay for (e.g. 'harvey-tools/scrape_url')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Your agent identifier (must be registered first)"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 (register it first)"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses meaningful behavior: it verifies limits, estimates ROI from prior spends, and suggests cheaper alternatives. It stops short of explicitly stating that it is read-only, whether it reserves budget, or what happens when a limit is exceeded.

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?

The description is three sentences, front-loads the core purpose, and contains no filler. Every sentence contributes either purpose, behavior, or timing.

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?

The description explains why and when to call the tool, but there is no output schema and it does not describe the return value or approval response. An agent can invoke it correctly, but still lacks guidance on interpreting or acting on the result.

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 all four parameters, including the category enum, are already documented in the schema. The description does not add parameter-level syntax or interpretation beyond mentioning category limits and service spending conceptually.

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 names a specific operation, 'Pre-spend budget approval check,' and enumerates three concrete checks: daily/weekly/category limits, ROI estimation from past spends, and cheaper alternatives. The phrase 'Call this BEFORE paying' also separates it from post-spend reporting/recording siblings.

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 clearly says when to call: before paying for any service. That is strong timing guidance, though it does not explicitly name when not to use it or identify alternative sibling tools.

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