Skip to main content
Glama

Preview Quote Tool

preview-quote
Read-only

Calculates a deterministic estimate preview without saving, sending, or creating a quote. Use to preview quote in the connected business. Returns document_type, customer_id, pricing, persisted, scope.

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": "preview-quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesEstimate line item.
tax_modeNoTax calculation mode: none or manual.
coupon_codeNoOptional coupon code evaluated by the authorized pricing service.
customer_idNoOptional resolved customer ID.
tax_rate_idNoBusiness-owned tax rate identifier for manual tax calculation.
document_discount_typeNoDocument-wide discount mode: none, percentage, or fixed.
document_discount_valueNoDocument-wide discount amount or percentage for the selected discount mode.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
pricingYesPricing data returned by the authorized safe projection.
persistedYesPersisted flag; previews do not perform this action.
customer_idYesCustomer id for the returned result.
document_typeYesType of the previewed document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / coupon_code / description
      Added value: +"Optional coupon code evaluated by the authorized pricing service."
    • addedInput schema / properties / document_discount_type / description
      Added value: +"Document-wide discount mode: none, percentage, or fixed."
    • addedInput schema / properties / document_discount_value / description
      Added value: +"Document-wide discount amount or percentage for the selected discount mode."
    • addedInput schema / properties / tax_mode / description
      Added value: +"Tax calculation mode: none or manual."
    • addedInput schema / properties / tax_rate_id / description
      Added value: +"Business-owned tax rate identifier for manual tax calculation."
    • addedInput schema / required
      Added value: +[
      +  "items"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "customer_id": {
      +      "description": "Customer id for the returned result.",
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "document_type": {
      +      "description": "Type of the previewed document.",
      +      "enum": [
      +        "estimate"
      +      ],
      +      "type": "string"
      +    },
      +    "persisted": {
      +      "description": "Persisted flag; previews do not perform this action.",
      +      "enum": [
      +        false
      +      ],
      +      "type": "boolean"
      +    },
      +    "pricing": {
      +      "description": "Pricing data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "document_type",
      +    "customer_id",
      +    "pricing",
      +    "persisted",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, and the description reinforces this with 'without saving, sending, or creating a quote' plus 'deterministic', which tells the agent repeated calls return identical results with no side effects. The mention of a 'persisted' return value is a useful behavioral signal, though it partially duplicates the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loads the most important fact (no persistence). The second sentence is weak: 'Use to preview quote in the connected business' is tautological, and the return-field list ('Returns document_type, customer_id, pricing, persisted, scope') duplicates the existing output schema.

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

Completeness4/5

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

With annotations covering the safety profile, 100% schema description coverage, and an output schema handling return values, the description only needs to convey the no-persistence guarantee, which it does explicitly. It could be stronger by stating that results are non-authoritative and differ from a created quote, but nothing essential 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 100%, so all seven parameters, including tax_mode, coupon_code, and the document-level discount fields, are already documented. The description adds no parameter-level meaning such as how coupon_code interacts with document_discount_type, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Calculates a deterministic estimate preview') with the crucial scope qualifier that nothing is saved, sent, or created. It does not name which sibling to use instead (e.g., get-quote for existing quotes, preview-invoice for invoices), so differentiation is left implicit.

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

Usage Guidelines2/5

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

The only usage sentence is 'Use to preview quote in the connected business,' which restates the purpose rather than telling the agent when to pick this over get-quote or the other preview-* tools. The 'without saving, sending, or creating' clause implies a when-to-use condition (pre-flight check before committing), but it is never framed as guidance.

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