Skip to main content
Glama

Propose issuing an invoice

invoices_issue

[Invoicing changes] Propose issuing an invoice (or a proforma). Simulated first; nothing is issued until the seller approves (asked in the conversation, confirmed with manage_action). After approval, get_action returns the series, number and the PDF link, which can be passed to orders_attach_invoice. Prices are WITH VAT unless vat_included is false. Sending it to SPV (e-Factura) is a separate step: invoices_send_efactura. Recording the payment: invoices_collect. Works on: Demo invoicing (sample data).

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": {
      "client": "<client>",
      "lines": "<lines>"
    },
    "name": "invoices_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
clientYes
seriesNoSeries name; default is the one set on the account.
accountNoAccount id from list_accounts. Optional when only one account is connected.
currencyNo
doc_typeNoDefault: invoice.
due_dateNoYYYY-MM-DD
languageNo
mentionsNo
issue_dateNoYYYY-MM-DD
order_numberNoMarketplace order id; used to warn about a possible duplicate.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the key behavioral trait that the call is a proposal/simulation that produces nothing until an explicit approval gate is passed, and how the result becomes retrievable via get_action. It does not cover retry/idempotency implications of re-proposing the same invoice or error behavior, so it stops short of full disclosure.

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?

A bracketed domain tag plus five tight sentences, each doing distinct work: purpose, approval gate, post-approval retrieval, VAT rule, sibling routing, environment scope. No repetition of the title or the schema, and the critical constraint (nothing is issued until approval) is front-loaded.

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?

The tool is complex (11 params, nested client and line objects, output schema present), and the description supplies everything an agent needs to sequence it correctly: draft-then-approve lifecycle, where the output goes via get_action, and which separate tools handle subsequent steps. Return format is left to the output schema, as appropriate.

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 55% across 11 parameters (including nested line items), so the description must carry weight — and it does for the most consequential ambiguity: "Prices are WITH VAT unless vat_included is false", which disambiguates the price/vat_included pair inside each line. It leaves most remaining parameters (client fields, currency, language, mentions, issue_date) to the schema, but the line-item semantics it adds are the ones that decide whether the invoice amounts are correct.

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 plus its variant scope ("Propose issuing an invoice (or a proforma)") and immediately separates itself from the neighboring tools by naming invoices_send_efactura, invoices_collect, orders_attach_invoice, get_action and manage_action. An agent can pick this over invoices_issue_for_order or orders_attach_invoice without opening any schema.

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?

Gives explicit when/what-happens-next guidance: a simulation runs first, nothing is issued until the seller approves in conversation and confirms with manage_action, and the follow-on steps (send to SPV, record payment, attach PDF to order) are each routed to the correct sibling. It also states the environment restriction ("Works on: Demo invoicing (sample data)"), which prevents a wrong-context call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources