InvoiceParser Pro

Preview: Set a monthly budget

preview_set_budget

Read-onlyIdempotent

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. This returns an exact preview and a five-minute confirmation token; it does not apply the change.

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

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description adds important behavior: it requires settings permission and confirmation, returns an exact preview plus a five-minute confirmation token, does not apply the change, and enforces finite nonnegative two-decimal values with no silent rounding.

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 compact and front-loaded, leading with the preview purpose before constraints and return behavior. Every sentence contributes useful information without repetition.

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 preview tool with no output schema, the description adequately explains that it returns an exact preview and a five-minute confirmation token and does not apply changes. A minor gap remains around what exactly the preview contains or how the token is subsequently consumed.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well by explaining that the budget is in an explicit ISO currency and that monthly amounts must be finite, nonnegative, and fit the two-decimal model without rounding. It adds less detail about the category field, but the core value semantics are covered.

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 action: preparing to create or update a category's standing monthly planning budget, and explicitly says it returns a preview and token rather than applying the change. This clearly distinguishes it from sibling set_budget, which performs the actual mutation.

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?

The description makes the use context clear by saying it prepares a budget change, requires confirmation, returns a token, and does not apply the change. It does not explicitly name set_budget as the follow-up tool, so the alternative is strongly implied but not formally stated.

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?