agent-verifier-mcp

create_budget

Set a spending limit for an AI agent in dollars, with optional currency and validity duration, to control purchases.

Instructions

Create a spending budget for this agent. Set a limit before making purchases.

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": {
      "amount_dollars": "<amount_dollars>"
    },
    "name": "create_budget"
  }
}

Input Schema

Name	Required	Description	Default
`currency`	No	Currency code (default: usd)	usd
`valid_hours`	No	How many hours the budget is valid (default: 24)
`amount_dollars`	Yes	Budget limit in dollars (e.g. 10.00 for $10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 25, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It states a creation action but lacks details on whether existing budgets are overridden, if multiple budgets can coexist, required permissions, or response behavior. This is insufficient for an AI agent.

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, no filler, front-loaded with purpose. Every word is necessary and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 annotations, the description should cover creation behavior, idempotency, and response. It only states what the tool does, not how it works or what to expect, leaving significant gaps for a 3-parameter tool.

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 coverage is 100%; all parameters have descriptions. The description adds 'set a limit' which aligns with amount_dollars but adds no new meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states the tool creates a spending budget for the agent and sets a limit before making purchases. It differentiates from sibling tools like check_budget and get_budget which are for querying, and refund/release which are for other actions.

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?

The description implies usage before purchases ('Set a limit before making purchases'), but does not explicitly provide when-to-use vs alternatives or any exclusion criteria. Sibling tools suggest other budget-related actions but no comparative guidance.

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

Deploy Server