Skip to main content
Glama

Create estimate (proforma)

create_estimate

Issue a proforma estimate for customer approval or payment before generating a final invoice.

Instructions

Issue a proforma (estimate) — a quote or payment request that is not yet a fiscal invoice. Returns { series, number, url }.

Use this when the customer needs something to approve or to pay against before being invoiced, or when the user asks for a quote, an offer or a proforma. Use create_invoice instead when the sale is final and a fiscal document is what's wanted.

Once the customer accepts, turn it into an invoice with create_invoice_from_estimate rather than building the invoice by hand. As with invoices, call list_taxes for valid VAT rates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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.
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.
seriesNameNoDocument series. Falls back to the configured default.
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.
companyVatCodeNoIssuing company CIF. Falls back to SMARTBILL_VAT_CODE.
delegateIdentityCardNoDelegate ID card series and number; only printed when delegateName is also sent.
Behavior5/5

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

Annotations only indicate non-read-only and non-destructive. Description adds that it creates a non-fiscal document, returns series/number/url, and is part of a lifecycle (estimate → invoice). No contradictions.

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?

Three sentences, front-loaded with purpose and return value, then usage guidance. Every sentence adds value; no wasted words.

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 tool with 21 parameters and no output schema, the description explains return value, lifecycle (create → convert), and links to related tools. It is sufficiently complete given the complexity.

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 100%, so baseline is 3. Description adds useful contextual guidance (e.g., 'As with invoices, call list_taxes for valid VAT rates'), but does not repeat schema descriptions. This raises it slightly above baseline.

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?

Clearly states it issues a proforma (estimate), not a fiscal invoice, and specifies return structure. Distinguishes from create_invoice by contrasting use cases.

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?

Explicitly says when to use (customer needs approval/payment before invoicing, user asks for quote/offer/proforma) and when to use create_invoice instead (final sale). Also advises using create_invoice_from_estimate after acceptance and calling list_taxes for VAT rates.

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