Skip to main content
Glama

Invoice Ninja: Create invoice

invoice-ninja_create_invoice

Invoice Ninja: Create a draft invoice for a client with line items, dates and notes. Creates an invoice as a draft and returns its number and totals. A draft is invisible to the client, stays out of the client balance and cannot reach anyone until you send it with send_invoice. Invoice Ninja numbers the invoice from the pattern in Settings > Generated Numbers, and without a due date the invoice is due immediately. Totals are quantity times unit cost per line, in the client currency. create_invoice runs without asking first: a draft reaches nobody and you can delete it in Invoice Ninja. Needs the user's Cotlet API key with access to this app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesLine items. Each has product (name from list_products or free text), description, unit_cost and quantity (decimals allowed).
companyNoCompany name, for accounts with several companies. Default: the company open when you signed in.
due_dateNoDefault: none, which makes the invoice due immediately.
client_idYesClient ID from list_clients or create_client.
po_numberNoThe client's purchase order number, printed on the PDF.
invoice_dateNoDefault: today.
public_notesNoNote the client sees on the invoice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=true): it discloses that a draft is invisible to the client, stays out of the client balance, cannot reach anyone, can be deleted, requires the Cotlet API key, and won't ask first. This is rich behavioral context an agent needs.

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?

Core action is front-loaded and each sentence is informative, but there is some redundancy: 'Create a draft invoice' and 'Creates an invoice as a draft' repeat, as do 'cannot reach anyone' and 'a draft reaches nobody'.

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?

For a mutation tool with no output schema, it covers return values (number and totals), the draft lifecycle, defaults, and auth requirements. Nothing essential to correct invocation is missing.

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 the baseline is 3. The description adds the totals computation (quantity times unit cost, in client currency) and numbering behavior, but the due-date-immediately point merely restates the schema's own default note, so added param-level meaning is marginal.

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 (create), resource (draft invoice), and scope (for a client with line items, dates and notes). It distinguishes itself from siblings like send_invoice and create_quote by emphasizing the draft state.

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?

Explains the draft context clearly and routes the agent to send_invoice as the step required to actually deliver the invoice, and notes it runs without confirmation. It doesn't explicitly contrast with create_quote or convert_quote_to_invoice, but the when-to-use context is solid.

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