InvoiceParser Pro

Create a client

create_client

Idempotent

Apply only the exact change returned by preview_create_client, after the user confirms that preview. Accepts its confirmation_token only; changed or expired records require a new preview. Prepare creation of a named client in the connected workspace. Requires confirmation and the existing workspace write entitlement.

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_client"
  }
}

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=false, destructiveHint=false and idempotentHint=true. The description adds real context beyond them: the confirmation gate, the requirement for the workspace write entitlement, and token expiry semantics. It does not say what happens on a rejected/expired token or what is returned, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences where two would do, and the ordering is inverted: the confirmation-token mechanics come before the statement of what the tool actually creates. 'Prepare creation of a named client' is a hedged, imprecise sentence that could be rewritten as a direct purpose statement.

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 single-parameter, preview-gated mutation with no output schema, the description covers the workflow, the prerequisite entitlement, and token invalidation. The main residual gap is the return value (e.g., the new client identifier) needed to chain into follow-up calls.

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?

Schema description coverage is reported as 0%, though the nested Confirmation def does describe confirmation_token, so the agent is not fully blind. The description reinforces that only the token is accepted and that it must come from this operation's preview, but it adds nothing about length bounds, reuse, or format beyond what the schema carries.

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?

The description names a specific verb and resource (create a named client in the connected workspace) and clearly separates itself from the sibling preview_create_client by framing this tool as the apply/confirm step. The phrase 'Prepare creation of a named client' is slightly muddy for what is actually a commit operation, and it appears after the token mechanics rather than front-loaded, but the intent is recoverable.

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?

Explicit when-to-use: only after preview_create_client has been called and the user confirms the displayed change. It also states when-not: 'Accepts its confirmation_token only; changed or expired records require a new preview,' which routes the agent back to the preview flow on stale tokens.

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?