Skip to main content
Glama

Create a draft quote

create_draft_quote

Use this when a connected user asks to create a quote, estimate or proforma invoice for a client. Saves a new draft quote (or proforma invoice) for a client of the business. It gets the next quote number. Line descriptions are printed on the tax invoice: write them in English, translating when the user writes in another language (for example "Консультация" becomes "Consultation"). Keep names, brands and model numbers exactly as written. Use another language only when the user explicitly asks for it or quotes the exact text. Lines are priced by Fatura Go as in the app (each line rounded, header = sum of lines; with prices_include_vat the entered price includes VAT, e.g. 26.95 = 25.67 + 1.28 VAT). Returns the stored lines and totals and app_url. Nothing is issued, numbered as a tax invoice or sent: the user reviews and issues it in Fatura Go ("Review and issue in Fatura Go"). valid_until defaults to 30 days from today. Do not use it for an invoice (create_draft_invoice) or to turn a quote into an invoice: that is Convert to invoice in Fatura Go.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "create_draft_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. Default today (UAE).
itemsYesThe lines, 1 to 100. On an update they replace every line.
notesNo
currencyNoOne of AED, SAR, USD, EUR, GBP, KWD, QAR, BHD, OMR, INR. Default the client's preferred currency, else the business currency.
client_idNoFrom list_clients or create_client.
quote_kindNoquote (default) or proforma.
business_idNoFrom list_businesses. May be left out when the connection shares exactly one business.
client_nameNoOnly when the client_id is not known: nothing is written, and the matching clients are returned to pick from.
valid_untilNoYYYY-MM-DD, on or after date.
idempotency_keyNoOptional. A unique string (for example a UUID) for this request: a retry with the same key returns the first result instead of writing again.
prices_include_vatNoWhether unit_price includes the 5% VAT. Default the business setting.
document_language_overrideNoLanguage this document prints in: en, ar or bilingual. Left out: a new draft follows the business setting and an update keeps the current choice; null goes back to the business setting. Only for a document the user asked to print in another language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / document_language_override
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 20,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Language this document prints in: en, ar or bilingual. Left out: a new draft follows the business setting and an update keeps the current choice; null goes back to the business setting. Only for a document the user asked to print in another language."
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only state readOnly=false, destructive=false and idempotent=false; the description carries far more than that. It discloses the non-obvious side effect of consuming the next quote number, states that nothing is issued, numbered as a tax invoice, or sent, explains rounding and VAT-inclusive pricing (26.95 = 25.67 + 1.28), and names the return payload (stored lines, totals, app_url).

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?

Usage and non-usage are front-loaded, then behavioral facts follow in dense, purposeful sentences. The one waste is the full repetition of the line-description language rule already present in the items schema, which lengthens the block without adding 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?

For a 12-parameter write tool with no output schema, the description covers the draft-only scope, numbering side effect, default validity window, pricing/VAT model, language policy, and the returned fields. Nothing an agent needs to call it safely and explain the result to a user is missing.

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 92% schema coverage the baseline is 3, but the description adds pricing semantics the schema does not state at the header level: each line is rounded and the header is the sum of lines, and valid_until defaults to 30 days from today. The language-translation rule for line descriptions is repeated verbatim from the schema, which limits the added value.

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 opens with a specific verb and resource ("Saves a new draft quote (or proforma invoice) for a client of the business") and adds the concrete side effect "It gets the next quote number." It distinguishes itself explicitly from create_draft_invoice, so an agent can choose between the two create tools without opening a 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 both when-to-use ("when a connected user asks to create a quote, estimate or proforma invoice for a client") and when-not-to-use with the alternative named ("Do not use it for an invoice (create_draft_invoice)"). It further routes the conversion case out of the tool system entirely: "Convert to invoice in Fatura Go."

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources