Skip to main content
Glama

Record a supplier bill

purchasing_create_bill

Record a bill a supplier sent, with their reference (their invoice number; the same reference from the same supplier is refused twice). Either its own lines (supplier and lines: each to its book account, default the supplier's; a sku line to the inventory account), or from an order (order, quantities: "received" (default) or "ordered"): what is not billed yet, at the order's costs. It is due due_date, default the issue date plus the supplier's terms. Attach its PDF from the file store with file_id; reading the PDF is your work. A carrier's or the customs office's bill marks the import VAT it passes on with import_vat on its line. When the account keeps books, it is posted to them. Costs $0.01 per call; nothing if it fails.

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": "purchasing_create_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
notesNo
orderNoThe order_id, or the order's number like "PO-0007".
accountNoWith order: the book account for its lines without a SKU. Default: the supplier's.
file_idNoA file_id from the file store.
currencyNoISO 4217, e.g. "EUR". Default: the supplier's.
due_dateNoYYYY-MM-DD
supplierNoA supplier_id, or the supplier's name.
referenceNo
issue_dateNoYYYY-MM-DD
quantitiesNoreceived
tax_treatmentNoreverse_charge: the supplier's invoice has no VAT because the business owes it (services from abroad, a reverse-charge trade at home); eu_goods: goods bought from another EU country. The lines' tax_rate is the rate owed; the VAT is owed and reclaimed at once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/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 key behaviors: the uniqueness constraint on supplier reference, the cost per call ($0.01) and that failures incur no charge, the posting to books when the account keeps books, and the special handling of import VAT. These details are crucial for an agent to understand consequences and constraints.

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?

The description is dense but every sentence carries necessary information. It is front-loaded with the main action, though the flow is a bit run-on; better structuring into shorter sentences or bullet-like clauses could improve readability without losing content.

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?

Given the complexity (12 parameters, two modes) and the absence of an output schema, the description covers the essential behavior: how lines and orders work, defaults, uniqueness, cost, and posting. It is largely complete, though it could mention permission requirements or error handling beyond duplicate references.

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 67%, and the description adds meaningful context for several parameters: it clarifies that reference is the supplier's invoice number, that lines go to the supplier's book account by default, that order (with quantities) pulls unbilled items at order costs, and that due_date defaults to issue_date plus supplier terms. It also explains file_id and import_vat. Some parameters like notes and issue_date lack description, but the added semantics are substantial.

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?

The description states a specific verb ('Record') and resource ('a bill a supplier sent'), clearly distinguishing it from sibling tools like purchasing_update_bill or purchasing_list_bills. It also covers the two main modes (own lines or from an order), making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by explaining the two modes and the default for quantities, but it does not explicitly say when to use this tool versus alternatives like purchasing_update_bill or purchasing_create_order. No when-not-to-use or prerequisite guidance is provided.

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