OrgLines

Invoices: Create invoice

invoice_create

Destructive

Issue an invoice in this company's invoices and render its PDF. Client: pass lead_id / organization_id / customer_id from invoice_list_clients, or 'client' = the client's NAME as the person said it — a role word («клієнт», «компанія», «замовник», «ТОВ») is not a name and is refused with the candidates; a name that matches no single client is refused too. A NEW client only with new_client=true and the real name (client_tax_id / client_iban / client_email only if the person gave them). Money: one 'amount' + 'description', or 'lines' for several items — numbers exactly as the person said, never computed or invented. 'currency' only if named (else the company's), 'vat_percent' only if VAT was stated (else the server picks the VAT regime from the seller entity's and the client's country and VAT ID — standard rate, reverse charge, export or no VAT — and the result's vat_regime names it; tell the person); prices_include_vat says whether the named prices already include it (default true). 'seller_legal_entity' (id or name) when the company has several legal entities. No payment links. Runs propose→confirm. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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

Input Schema

Name	Required	Description
`note`	No	A note printed for the client.
`lines`	No	The person's own lines, when there is more than one item. Prices exactly as said.
`amount`	No	The total the person named.
`client`	No	The client's name as the person said it (Олена, ТОВ Ромашка).
`lead_id`	No
`currency`	No
`due_days`	No
`new_client`	No	Create a NEW client with this exact name (the person asked).
`client_iban`	No
`customer_id`	No
`description`	No	What for, in the person's words.
`vat_percent`	No
`client_email`	No
`client_tax_id`	No
`organization_id`	No
`prices_include_vat`	No
`seller_legal_entity`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses the propose→confirm flow, the exact status='confirmation_required' response with action_id and plan_token, and that the write only happens after confirm_action. It also explains server-side VAT regime selection and refusal behavior, which are important behavioral traits for a destructive write tool.

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 and front-loads the purpose, client rules, money rules, and confirmation flow. It is appropriately sized for a 17-parameter destructive tool, though some clauses are packed into long sentences and could be slightly easier to scan.

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 complex mutation tool with no output schema and sparse annotations, the description covers the critical behavior: client identification, money handling, VAT fallback, legal entity selection, refusal rules, and the confirmation gate. Minor contextual gaps remain around fields like due_days and what the final result contains after confirmation.

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?

With only 35% schema description coverage across 17 parameters, the description compensates well for key fields: client name semantics, new_client, client_tax_id/client_iban/client_email only if given, amount versus lines, currency default, VAT default and regime selection, prices_include_vat default, and seller_legal_entity. It leaves some lower-detail parameters such as due_days and note to the schema, so it is strong but not exhaustive.

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 and resource: 'Issue an invoice in this company's invoices and render its PDF.' It clearly distinguishes creation from client lookup by directing ID sourcing to invoice_list_clients and confirmation to confirm_action, so an agent can identify the tool without opening another 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?

It gives explicit usage rules: pass lead_id/organization_id/customer_id from invoice_list_clients, use 'client' only as the person's stated name, refuse role words and non-matching names, create a new client only with new_client=true, and use either amount/description or lines. It also names the confirmation alternative confirm_action and states 'No payment links.'

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

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?