Skip to main content
Glama

Create invoice

create_invoice

Issue a new invoice for a normal sale in SmartBill Cloud. Returns the document series, number, and a direct URL to the invoice.

Instructions

Issue a new invoice (factura) in SmartBill for a normal sale. Returns { series, number, url }, where url links to the document in SmartBill Cloud.

Before calling: use list_taxes to get valid taxName/taxPercentage values rather than guessing a VAT rate, and list_series if you do not know which series to issue into.

Do not use this to invoice an existing proforma — use create_invoice_from_estimate, which links the two documents. Do not use it to reverse an invoice — use create_reverse_invoice.

An issued invoice is a fiscal document that generally cannot be deleted afterwards. Confirm the client, the amounts and the VAT rate with the user before calling, and pass isDraft: true while details are still unsettled — a draft can be edited or discarded in SmartBill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
avizNoDelivery note number when invoicing an aviz.
emailNoEmail overrides used when sendEmail is true.
clientYesThe client the document is issued to.
dueDateNoDue date (YYYY-MM-DD).
isDraftNoIssue as a draft instead of a final document.
paymentNoRecord a payment at the same time as the invoice is issued.
currencyNoDocument currency. Default RON.
languageNoDocument language: RO, EN, DE, IT, ES, FR, HU. Default RO.
mentionsNoFree text printed on the document.
productsYesLine items on the document.
useStockNoDeduct the invoiced quantities from stock.
issueDateNoIssue date (YYYY-MM-DD). Defaults to today at SmartBill.
issuerCnpNoPersonal numeric code of the issuing person.
precisionNoNumber of decimals used for amounts. Default 2.
sendEmailNoEmail the document to the client on issue.
issuerNameNoName of the issuing person.
paymentUrlNoPayment link printed on the PDF.
seriesNameNoDocument series. Falls back to the configured default.
colectedTaxNoCollected VAT amount, when usePaymentTax is true.
paymentBaseNoCollected base amount, when usePaymentTax is true.
paymentDateNoDate of the payment recorded with the invoice.
delegateAutoNoDelegate vehicle; only printed when delegateName and delegateIdentityCard are also sent.
delegateNameNoPerson collecting the goods (delegat), printed on the document.
deliveryDateNoDelivery date (YYYY-MM-DD).
exchangeRateNoExchange rate to RON when currency is not RON.
observationsNoInternal note; not printed on the document.
paymentTotalNoTotal collected, when usePaymentTax is true.
usePaymentTaxNoApply VAT on collection (TVA la incasare).
companyVatCodeNoIssuing company CIF. Falls back to SMARTBILL_VAT_CODE.
delegateIdentityCardNoDelegate ID card series and number; only printed when delegateName is also sent.
Behavior4/5

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

The description discloses that an issued invoice generally cannot be deleted afterwards, which is critical behavioral context beyond the annotations. It also mentions the return format. However, it does not elaborate on authentication or rate limits, but given the annotations' limited scope, this is sufficient.

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?

The description is five sentences with no fluff, front-loading the purpose and return value, followed by prerequisites, exclusions, and consequences. Every sentence adds essential information.

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?

Given the tool's complexity (30 parameters, nested objects, no output schema), the description covers purpose, return type, prerequisites, exclusions, and a critical post-condition (inability to delete). The schema handles parameter details, leaving the description to fill contextual gaps, which it does effectively.

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?

The input schema has 100% coverage with descriptions for all parameters. The description adds some high-level guidance (e.g., using list_taxes for valid tax values), but does not add significant per-parameter meaning beyond what the schema provides.

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 clearly states the tool issues a new invoice for a normal sale, specifying the resource (invoice in SmartBill) and action (create). It also distinguishes itself from sibling tools like create_invoice_from_estimate and create_reverse_invoice by explicitly stating what not to use it for.

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?

The description provides explicit guidance on when to use the tool (normal sale) and when not to (invoice from proforma, reverse invoice). It also advises using list_taxes and list_series beforehand, and instructs to confirm details with the user and use isDraft for unsettled cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bogdanripa/smartbill-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server