InvoiceParser Pro

Create an automation rule

create_automation_rule

Idempotent

Apply only the exact change returned by preview_create_automation_rule, after the user confirms that preview. Accepts its confirmation_token only; changed or expired records require a new preview. Prepare an active rule for future matching invoices. Currency-bound money conditions and existing guards apply. External export/notification actions use IPP. Requires approval-scope 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": "create_automation_rule"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations, the description explains the preview-confirmation workflow, token invalidation behavior, guard conditions, currency-bound money constraints, and that external export/notification actions use IPP. These details materially expand the agent's understanding of the operation's safety and prerequisites.

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 critical constraint—apply only the exact previewed change after confirmation—is front-loaded. Subsequent sentences are short and each adds a relevant behavioral constraint, with no wasted prose.

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 confirmation-token mutation with annotations already covering idempotency and non-destructiveness, the description supplies the full workflow context: preview dependency, user confirmation, token expiry, guard conditions, and approval requirements. Nothing essential for correct invocation is 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 single parameter is well explained: the description says only the exact confirmation_token from the preview is accepted and that changed or expired records require a new preview. Although schema description coverage is reported as 0%, the schema itself also documents the token, and the description adds the crucial validity and one-token-only semantics.

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: apply the exact change from preview_create_automation_rule and prepare an active rule for future matching invoices. It clearly distinguishes this execution step from the preview sibling and from other automation-rule tools like update/delete/list.

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 to use this only after the user confirms the preview and only with the confirmation_token from that preview. It also states that changed or expired records require a new preview and that approval-scope confirmation is required, giving clear when-to-use and when-not-to-use conditions.

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?