InvoiceParser Pro

Change workspace preferences

update_workspace_preferences

DestructiveIdempotent

Apply only the exact change returned by preview_update_workspace_preferences, after the user confirms that preview. Accepts its confirmation_token only; changed or expired records require a new preview. Prepare setup goal, preferred provider, currency/locale/timezone or routine choices. Does not connect a provider, change tax treatment or enable automatic export. Requires 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": "update_workspace_preferences"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already declare non-read-only, idempotent, destructive, and closed-world behavior. The description adds important behavioral context beyond annotations: confirmation is required, only the preview token is accepted, stale records require a new preview, and certain related changes are explicitly out of scope. It does not fully explain the destructive effect beyond the preference change itself, so it is strong but not exhaustive.

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 critical instruction is front-loaded: apply only the exact previewed change after confirmation. The content is efficient and structured, though the final sentence 'Requires confirmation' slightly repeats the opening sentence.

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 one-parameter mutation tool with rich annotations and no output schema, the description provides the necessary context: the required preview step, confirmation gate, token-only parameter, stale-token handling, covered preference categories, and explicit exclusions.

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 schema description coverage reported as 0%, the description carries the burden for the single confirmation_token parameter. It explains the token must be the exact one returned by the preview, must follow user confirmation, and that changed or expired records require a new preview, which adds meaningful semantics beyond the schema.

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: apply the exact change returned by preview_update_workspace_preferences, only after confirmation. It clearly distinguishes this mutation tool from its preview sibling and names the categories covered, so an agent can identify its role without opening the schema.

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 says when to use this tool: after the user confirms the preview, using only that preview's confirmation_token. It also states when not to proceed by noting changed or expired records require a new preview, and it lists operations this tool does not perform.

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?