Simpler.Asia

invoice_recurring_skip

Skips a recurring template's next invoice: next_due moves one period on (the template's own weekly, monthly or yearly day) and no invoice is made. A skip does not count toward max_invoices. Refuses NOT_FOUND for an id outside your tenant (call invoice_recurring_list) and CONFLICT when the template has ended (raise ends_on or max_invoices with invoice_recurring_update) or changed since expected_updated_at (read it again). Each call skips one run: to skip the run after, send expected_updated_at from this answer. Nothing is sent. NEXT: invoice_recurring_read.

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": {
      "id": "<id>"
    },
    "name": "invoice_recurring_skip"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The recurring template whose next invoice to skip (invoice_recurring_list shows ids).
`expected_updated_at`	No	Optional compare-and-set guard: the updated_at you last read. A mismatch returns CONFLICT and changes nothing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: next_due shifting, no invoice generated, skips not counting toward max_invoices, NOT_FOUND for out-of-tenant ids, CONFLICT on ended templates or stale expected_updated_at, and 'Nothing is sent'. Consistent with idempotentHint=false via 'Each call skips one run'.

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?

Front-loaded with purpose and effect, then refusal semantics, then next-step routing. Dense but every sentence carries actionable information; only mildly crowded with parenthetical asides.

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?

No output schema, and this is a nuanced mutation with non-obvious side effects (max_invoices exclusion, tenant scoping, optimistic locking). The description covers all of these, so an agent can invoke it correctly without further inference.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the workflow meaning of expected_updated_at ('send expected_updated_at from this answer' to skip the following run), which goes beyond the schema's generic compare-and-set wording.

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?

States a precise verb+resource: 'Skips a recurring template's next invoice', and immediately clarifies the effect ('next_due moves one period on ... and no invoice is made'). This clearly distinguishes it from siblings like invoice_recurring_update/delete/list/read.

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?

Explicitly routes the agent: call invoice_recurring_list to find ids, use invoice_recurring_update (raise ends_on or max_invoices) when the template has ended, re-read on CONFLICT, and 'NEXT: invoice_recurring_read'. It also states one skip per call and how to skip consecutive runs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Simpler.Asia 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?