Skip to main content
Glama

Periodieke factuur

save_recurring_invoice
Destructive

Create, change, or stop recurring invoices scheduled every 1, 3, or 12 months; Bookiz prepares a draft on each date for owner approval.

Instructions

Create (omit id), change or stop (active: false) an invoice that repeats every 1, 3 or 12 months, for example a monthly retainer. On each date Bookiz prepares a draft, never a final invoice; get_overview reports the draft and the owner approves it as usual.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_recurring_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
noteNo
linesNo
activeNo
next_dateNoThe first date a draft should be prepared
contact_idNo
every_monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a mutating, destructive, closed-world tool, and the description adds genuinely new behavior: Bookiz only prepares a draft, never a final invoice, and the owner must approve it through get_overview. That head-off is valuable for a destructive-flagged tool. It does not say what happens to existing drafts or prior generated invoices when a schedule is stopped or changed.

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?

Two dense sentences with the modes front-loaded and the cadence and draft-only caveat following. The parentheticals earn their place, though the second sentence packs workflow detail that could be split for readability.

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 7-parameter, zero-required mutation tool with no output schema, the description covers the modes, cadence constraints, and the lifecycle outcome well enough to call it correctly. The main gap is that it never says what fields a new schedule requires (line items, contact) versus what may be omitted on an update.

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 only 14%, so the description must compensate. It explains id (omit to create), active:false (stop), and every_months values (1, 3, 12), and implies the meaning of next_date, but leaves lines, contact_id, and note entirely undocumented — half the parameters carry no semantics anywhere.

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?

Names the specific resource (a repeating invoice) and enumerates the exact operating modes — create by omitting id, change, and stop via active:false — plus the permitted cadences (1, 3, 12 months) and the draft-only outcome. This clearly separates it from create_invoice/finalize_invoice and from list_recurring_invoices.

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?

The mode-selection rules are explicit and actionable (omit id to create, active:false to stop), and it points to get_overview for the resulting draft. It stops short of stating prerequisites or when to prefer this over create_invoice for a one-off invoice, but the trigger conditions are otherwise clear.

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