Skip to main content
Glama

Issue invoice

crunch_issue_invoice
Destructive

Issues a draft sales invoice by assigning its invoice number and posting it to your accounts. This action is final and does not email the customer.

Instructions

Issue a draft sales invoice: it gets its invoice number and is posted to your accounts. This is final (correct mistakes afterwards with a credit note in Crunch). It does not email the customer; see crunch_email_invoice.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "crunch_issue_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
invoice_idYesInvoice ID (see crunch_list_invoices); not the invoice number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=false; the description adds the crucial consequence beyond that: the action is final, assigns a number, and posts to the accounts. It also rules out side effects an agent might assume from an "issue" action, namely customer emailing. The correction path (credit note) is named but no error behavior is described.

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 its consequence, then the finality warning, then the alternative-routing pointer. No redundant restatement of the name or title.

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 two-parameter, non-idempotent mutation with no output schema, the description covers the essential risks: irreversibility, numbering/posting effects, and the no-email boundary. It could go one step further by noting what a successful call returns (e.g. the assigned invoice number).

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 100%, so baseline is 3. The description reinforces that this acts on a draft invoice and hints the ID refers to an existing invoice, but the "not the invoice number" distinction and the list-invoices pointer are already in the schema, and dry_run is not mentioned at all in the description.

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 specific verb and resource ("Issue a draft sales invoice") plus the concrete effect: it gets its invoice number and is posted to accounts. The closing sentence distinguishes it from the asset-emailing sibling by name, so an agent can separate the two without opening schemas.

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?

Makes clear this is the finalization step for a draft and explicitly points elsewhere for emailing (crunch_email_invoice) and for correcting mistakes (credit note). It never states hard preconditions or exclusions, e.g. that the invoice must already exist in draft state or what happens if it is already issued.

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

Deploy Server

Other Tools