Skip to main content
Glama
Sign In

Conecto Invoices

by chat.conecto
OverviewDiscussionsAdmin

Create a quote or invoice

invoices_create

Create a quote or an invoice as a draft: the customer (a CRM contact or company, or a name and email), line items, currency and dates. Nothing is numbered or sent yet; change drafts with invoices_update and send them with invoices_send. Amounts are the business's money in the document's currency, rounded half-up line by line. Costs $0.01 per call; nothing if it fails.

Input Schema

NameRequiredDescriptionDefault
kindYes
itemsYes
notesNoPrinted above the lines, e.g. "Thank you for your order" or a project reference.
currencyNoISO 4217, e.g. "USD", "EUR" or "JPY".
customerYesWho the document is for. Link a CRM record with contact_id or company_id, or give name and email (an email that matches a CRM contact links it). What is given here is printed as it is.
due_dateNoInvoices. Default: issue date + the payment terms.
e_invoiceNoInvoices and their credit notes as EN 16931 e-invoices (German B2B invoices must be from 2027): factur-x (Factur-X/ZUGFeRD, the XML inside the PDF/A-3) or xrechnung (XRechnung 3.0, its own XML beside the PDF), checked against the EN 16931 schema before sending. "" is the default: none, except that from 2027 an invoice from a German business to a German business above EUR 250 is a factur-x; "none" opts out (a business under the EUR 800,000 turnover allowance until 2028). Needs the customer's country. Default: the profile's.
issue_dateNoDefault: the day it is sent.
supply_dateNoInvoices: the day the goods or services were supplied, or the first day of a period. Default: the issue date, which the invoice then states.
valid_untilNoQuotes. Default: issue date + the profile's quote_valid_days.
payment_linkNoAn https link to pay this document. Default: the profile's payment_link.
supply_untilNoInvoices: the last day of the supply period, e.g. a month of service.
tax_exemptionNoWhy lines with tax_rate 0 carry no tax, printed on the invoice as the law asks: exempt, zero_rated, reverse_charge (the customer accounts for the VAT), intra_eu (goods to a business in another EU country), export (goods leaving the EU), outside_scope, small_business (a business under its country's small-business VAT exemption, such as UStG §19 or art. 293 B CGI: no line may carry tax). Needed in the EU for any line without tax. Default: the profile's.
vat_exchange_rateNoFor an invoice in another currency than the national one of the business's country: one unit of it in the national currency, for the VAT shown in both. Default in the EU: the European Central Bank's rate for the day of supply; UK businesses give it.
payment_terms_daysNoInvoices: days to pay, instead of the profile's terms.
tax_exemption_noteNoThe wording printed for the exemption instead of the standard one, e.g. "Steuerbefreit als Kleinunternehmer nach § 19 UStG".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations only cover readOnly/idempotent/destructive flags, and the description adds genuinely non-derivable traits: the result is an unnumbered draft, amounts are rounded half-up per line, the call costs $0.01, and nothing is charged on failure. It stops short of saying what the tool returns (e.g. the draft identifier), which matters for a create call with no output schema.

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?

Four short sentences: what it creates, the draft-state consequence, the rounding rule, and the cost. The most decision-relevant facts (draft, not sent) are front-loaded and nothing is repeated from the schema.

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 16-parameter, nested, no-output-schema create tool, the description covers the essentials an agent needs before calling: draft semantics, currency/rounding, cost, and next steps. The only meaningful gap is the return value (the created draft/id), which an agent would want given there is no output schema.

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 already 88%, so baseline is 3; the description adds real value by clarifying that amounts are stated in the business's money in the document's currency and are rounded half-up line by line. It also summarizes the customer input modes (CRM contact/company vs name and email). It does not add meaning for the many tax/e-invoice/date parameters, but the schema already documents those richly.

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 gives a precise verb and resource ("Create a quote or an invoice as a draft") and names the two lifecycle siblings, invoices_update and invoices_send. An agent can distinguish this from invoices_update, invoices_send, invoices_convert_quote and invoices_create_credit_note 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?

"Nothing is numbered or sent yet; change drafts with invoices_update and send them with invoices_send" states the condition that selects this tool and explicitly routes the agent to the alternative for each follow-up step. No exclusions are left to inference.

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

All Conecto Invoices toolsInspect
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