Skip to main content
Glama

Create quote (draft)

create_quote

Create a Draft quote (devis) for a company. Quotes are not fiscal documents - no certification. Dates default server-side (issue today, due/valid +30 days). Requires a matter id (dossier) the quote belongs to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesLine items in display order (1-100).
notesNoFree text printed on the quote (max 2000 characters).
currencyNoISO 4217 currency code. Defaults to EUR.
due_dateNoDue date, YYYY-MM-DD. Defaults to +30 days.
matter_idNoOptional matter (dossier) UUID the quote belongs to.
company_idYesThe client company UUID.
issue_dateNoIssue date, YYYY-MM-DD. Defaults to today.
valid_untilNoQuote validity limit, YYYY-MM-DD. Defaults to +30 days.
payment_termsNoPayment terms printed on the quote. Defaults to Net-30.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesQuote UUID.
typeYesDocument type: invoice, credit_note, provision or quote.
statusYesDocument status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.
currencyYesISO 4217 currency code (EUR, USD, GBP or CHF).
due_dateYesDue date, YYYY-MM-DD.
net_totalYesTotal excl. VAT, in the document currency.
tax_totalYesVAT amount, in the document currency.
issue_dateYesIssue date, YYYY-MM-DD.
gross_totalYesTotal incl. VAT, in the document currency.
valid_untilYesValidity limit, YYYY-MM-DD.
invoice_numberYesQuote number (own series).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedInput schema / properties / currency / description
      Added value: +"ISO 4217 currency code. Defaults to EUR."
    • changedInput schema / properties / due_date / description
      Previous value: -"Defaults to +30 days."New value: +"Due date, YYYY-MM-DD. Defaults to +30 days."
    • changedInput schema / properties / issue_date / description
      Previous value: -"Defaults to today."New value: +"Issue date, YYYY-MM-DD. Defaults to today."
    • addedInput schema / properties / items / description
      Added value: +"Line items in display order (1-100)."
    • addedInput schema / properties / items / items / properties / description / description
      Added value: +"Line text printed on the quote (1-500 characters)."
    • addedInput schema / properties / items / items / properties / display_order / description
      Added value: +"0-based position on the quote. Defaults to the array order."
    • changedInput schema / properties / items / items / properties / line_type / description
      Previous value: -"Defaults to 'item'."New value: +"Line kind: 'item' (billable, needs quantity and unit_price), 'section' (visual header) or 'description' (text-only sub-line). Defaults to 'item'."
    • changedInput schema / properties / items / items / properties / quantity / description
      Previous value: -"Required for 'item' lines."New value: +"Quantity. Required for 'item' lines."
    • changedInput schema / properties / items / items / properties / tax_rate / description
      Previous value: -"VAT percent. Omit to use the tenant default — never ask the user."New value: +"VAT percent (0-100). Omit to use the tenant default - never ask the user."
    • changedInput schema / properties / items / items / properties / unit_price / description
      Previous value: -"Required for 'item' lines."New value: +"Unit price excl. VAT, in the quote currency. Required for 'item' lines."
    • addedInput schema / properties / notes / description
      Added value: +"Free text printed on the quote (max 2000 characters)."
    • addedInput schema / properties / payment_terms / description
      Added value: +"Payment terms printed on the quote. Defaults to Net-30."
    • changedInput schema / properties / valid_until / description
      Previous value: -"Quote validity limit. Defaults to +30 days."New value: +"Quote validity limit, YYYY-MM-DD. Defaults to +30 days."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "currency": {
      +      "description": "ISO 4217 currency code (EUR, USD, GBP or CHF).",
      +      "type": "string"
      +    },
      +    "due_date": {
      +      "description": "Due date, YYYY-MM-DD.",
      +      "type": "string"
      +    },
      +    "gross_total": {
      +      "description": "Total incl. VAT, in the document currency.",
      +      "type": "number"
      +    },
      +    "id": {
      +      "description": "Quote UUID.",
      +      "type": "string"
      +    },
      +    "invoice_number": {
      +      "description": "Quote number (own series).",
      +      "type": "string"
      +    },
      +    "issue_date": {
      +      "description": "Issue date, YYYY-MM-DD.",
      +      "type": "string"
      +    },
      +    "net_total": {
      +      "description": "Total excl. VAT, in the document currency.",
      +      "type": "number"
      +    },
      +    "status": {
      +      "description": "Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.",
      +      "type": "string"
      +    },
      +    "tax_total": {
      +      "description": "VAT amount, in the document currency.",
      +      "type": "number"
      +    },
      +    "type": {
      +      "description": "Document type: invoice, credit_note, provision or quote.",
      +      "type": "string"
      +    },
      +    "valid_until": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Validity limit, YYYY-MM-DD."
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "invoice_number",
      +    "type",
      +    "status",
      +    "issue_date",
      +    "due_date",
      +    "valid_until",
      +    "currency",
      +    "net_total",
      +    "tax_total",
      +    "gross_total"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

It discloses useful server-side defaults for issue/due/valid dates and the non-certification nature of quotes. However, it does not describe side effects, validation behavior, or the fact that the created quote remains a draft (beyond the title), and it contains an inaccurate 'requires a matter id' claim.

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 short, front-loaded, and contains no redundant wording. It conveys the most important facts in two sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, return values need not be explained, but the description omits guidance on related workflow steps (e.g., send/accept/convert) and contains a requirement contradiction with the schema. It is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes all parameters in detail, and the description adds only default-date behavior. It incorrectly claims a matter id is required when the schema marks matter_id as optional, which undermines parameter understanding.

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 states the core action clearly: 'Create a Draft quote (devis) for a company.' It also distinguishes quotes from fiscal documents, making the tool's purpose easy to understand.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives some guidance by noting the draft state and that quotes are not fiscal documents, but it does not explicitly contrast this with related sibling tools such as send_quote or convert_quote_to_invoice, nor does it state when to prefer this tool.

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.