InvoiceParser Pro

Preview: Acknowledge an invoice warning

preview_acknowledge_invoice_warning

Read-onlyIdempotent

Prepare acknowledging a current warning or information flag. Errors cannot be acknowledged or bypassed. Requires 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_acknowledge_invoice_warning"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that ("does not apply the change"). It adds genuinely useful context beyond the annotations: an exact preview is returned along with a five-minute confirmation token, so the agent learns this is a two-step, time-bounded flow. It does not explain what 'requires confirmation' means concretely, since no confirmation parameter exists in the schema.

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?

Three short sentences, front-loaded with the action and followed by the constraint and the return behavior. No redundancy or filler.

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 one-parameter preview tool with no output schema, the description covers the return value (exact preview plus token) and the non-mutating nature. The only gap is how the token is supplied to the subsequent apply call, which is not represented in the input schema and is left unexplained.

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?

The single input object has 0% schema description coverage, and the description only indirectly hints at flag_type by saying 'warning or information flag'. It says nothing about invoice_id or the optional field property, so it fails to compensate fully for the undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: preparing an acknowledgement of a warning/information flag, and explicitly says it does not apply the change, which separates it from the sibling acknowledge_invoice_warning. It never names that sibling explicitly, so the preview/apply pairing must be inferred from the name prefix.

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?

Gives a clear condition for use (current warning or information flag) and an explicit exclusion (errors cannot be acknowledged or bypassed), plus the note that confirmation is required. It stops short of saying the follow-up step is acknowledge_invoice_warning with the returned token, which would complete the routing.

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?