InvoiceParser Pro

Set a monthly budget

set_budget

DestructiveIdempotent

Apply only the exact change returned by preview_set_budget, after the user confirms that preview. Accepts its confirmation_token only; changed or expired records require a new preview. Prepare creating or updating a category's standing monthly planning budget in an explicit ISO currency. Finite nonnegative values must fit the existing two-decimal budget model; no silent rounding. Requires settings permission and confirmation.

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": {
      "input": "<input>"
    },
    "name": "set_budget"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that settings permission and confirmation are required, that only the confirmation_token is accepted, that stale or changed previews require a new preview, and that budget values must be finite, nonnegative, two-decimal, and must not be silently rounded. This adds substantial operational context for a destructive mutation.

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?

The core instruction and prerequisite are front-loaded and every sentence contributes relevant context. However, the phrase 'Prepare creating or updating...' is slightly awkward, and the description is dense enough that some validation details could be mistaken as direct parameters rather than preview context.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, confirmation-gated mutation with one token parameter, the description covers prerequisites, permission requirements, token lifecycle, validation constraints, and stale-preview handling. Given the annotations and absence of an output schema, no critical invocation context appears missing.

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

Parameters5/5

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

The schema exposes only an input object containing confirmation_token, and the description adds important semantics: the token must be from the preview, must follow user confirmation, and cannot be reused if the underlying record changed or expired. It also clarifies that no budget values are passed directly to this tool.

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 states a specific verb and resource: applying the exact change returned by preview_set_budget to create or update a category's standing monthly planning budget. It also distinguishes this tool from its preview sibling by making the preview-then-confirm workflow explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs the agent to call this only after preview_set_budget and only after the user confirms that preview. It also states that changed or expired records require a new preview, leaving no ambiguity about when this tool should be invoked.

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

All InvoiceParser Pro 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.

Resources

Need Help?