Conecto Invoices

Set the business details

invoices_set_profile

Idempotent

Set the business details printed on quotes and invoices: legal name, country, address, tax ID, email, phone, logo, default currency, payment terms, tax rate, number prefixes and next numbers, payment instructions, an optional payment link and legal notes. Only the fields given change. Sending needs legal_name and country; in the EU, the UK and Switzerland an invoice also needs the address and tax ID, checked when it is sent. Costs $0.001 per call; nothing if it fails.

Input Schema

Name	Required	Description
`email`	No	Where customers write about invoices: printed, and the Reply-To of emails.
`paper`	No	Default: Letter for USD and CAD businesses, else A4.
`phone`	No
`footer`	No	Payment instructions printed at the bottom of invoices, e.g. bank name, IBAN and BIC.
`tax_id`	No	VAT, GST or tax number, printed with the address.
`address`	No	Postal address, one line per row.
`country`	No	ISO 3166-1 code of the country the business is established in, e.g. "DE". Needed to send: it decides what invoices must show (in the EU the VAT ID, addresses, the date of supply, why a line has no tax, VAT in the national currency) and is checked before each one goes out.
`currency`	No	Default currency of new documents, ISO 4217.
`tax_rate`	No	Default tax percent for new lines, e.g. 19. 0 for none.
`timezone`	No	IANA time zone for dates, e.g. "America/New_York". Default UTC.
`e_invoice`	No	Invoices 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.
`tax_label`	No	What the tax is called on documents: "VAT", "GST", "Sales tax". Default "Tax".
`legal_name`	No	The business name on documents; also the email sender name.
`pay_online`	No	A Pay button on each invoice's page: Stripe Checkout on the business's own Stripe (connect it with invoices_connect_stripe); each payment is recorded and posted to the books on its own. $0.10 per invoice paid online.
`legal_notes`	No	Printed at the foot of every quote, invoice and credit note: the company register and managing directors, a small-business VAT note, late-payment terms the law asks for (France: penalty rate and the EUR 40 indemnity). In France and Germany the country's default wording is filled in when the country is set and none is given; "" brings it back.
`logo_file_id`	No	An image in the file store (PNG, JPEG, GIF, WebP or SVG, up to 1 MB). "" removes the logo.
`payment_link`	No	An https link where customers pay, e.g. the business's own Stripe Payment Link. "" removes it.
`quote_prefix`	No	Default "Q-".
`tax_exemption`	No	Why 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.
`invoice_prefix`	No	Default "INV-": invoices are INV-0001, INV-0002...
`quote_valid_days`	No	How long quotes stay open. Default 30.
`document_language`	No	The language of the fixed words on quotes, invoices and credit notes (labels, dates, amounts); "" picks it by country: German in Germany and Austria, French in France, else English. The business's own text is printed as written.
`next_quote_number`	No
`credit_note_prefix`	No	Default "CN-".
`payment_terms_days`	No	Days from issue to due date. Default 14.
`tax_exemption_note`	No	The wording printed for the exemption instead of the standard one, e.g. "Steuerbefreit als Kleinunternehmer nach § 19 UStG".
`next_invoice_number`	No	The number the next invoice gets, e.g. to carry on from another tool. Never one already used.
`next_credit_note_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

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, idempotent=true, destructive=false): it discloses the partial-update rule, send-time validation requirements, the $0.001 per-call cost with no charge on failure, the $0.10/online-payment cost surfaced via pay_online, and legal e-invoicing/legal-notes defaulting behavior. This is material context an agent could not infer from the structured fields.

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?

Front-loads the core action and field scope, then adds prerequisite and cost sentences that earn their place. The long mid-sentence field enumeration partly duplicates the schema but is not wasteful enough to penalize heavily.

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 28-parameter profile setter with no output schema, the description covers the partial-update contract, required-when-sending fields, legal validation behavior, costs, and defaulting rules. Nothing an agent needs to call it correctly 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 89%, so the schema already documents nearly all 28 parameters in detail; the description mostly re-lists the same field names without adding syntax or format meaning beyond it. Baseline 3 applies since the schema carries the semantic load.

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 ("Set") and resource ("business details printed on quotes and invoices") and enumerates the scope of fields, from legal name to number prefixes and e-invoicing. An agent can distinguish this from the read counterpart invoices_get_profile without opening either schema.

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?

Gives clear context: "Only the fields given change" establishes partial-update semantics, and "Sending needs legal_name and country; in the EU, the UK and Switzerland an invoice also needs the address and tax ID" states prerequisites and when validation is enforced. It does not explicitly route to alternatives (e.g. invoices_get_profile to read), which holds it below a 5.

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

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