Skip to main content
Glama

Draft a priced, VAT-correct quote

draft_quote

Price a job after a site visit. Give the job, customer, labour (time, priced from the saved rate), materials (trade cost, marked up), other costs and optional extras; the server applies VAT correctly (registered or not, 20/5/0%, the construction domestic reverse charge for contractor customers), the deposit rule, validity, exclusions and a running quote number. Returns the totals, the trade-only margin view, warnings, a check_before_sending list of commonly forgotten items for that trade, and the links to the PDF and the customer's phone page (a DRAFT until finalise_quote). from_quote copies a past quote's lines for a new customer. save false returns the numbers without saving.

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": {
      "trade_key": "<trade_key>",
      "title": "<title>",
      "customer": "<customer>"
    },
    "name": "draft_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoDefault true. false = preview the numbers only, nothing saved, no quote number used.
notesNoAnything else the customer should read.
otherNoOther costs charged as a set amount in pounds (ex VAT): skip hire, scaffolding, waste disposal, certification or notification fees, parking. qty multiplies the amount (for example scaffold per week).
startNoLikely start, for example "w/c 7 December".
titleYesShort job name the customer sees, for example "Full rewire, 3 bedroom semi" or "Replace combi boiler".
tradeNoWhich trade this job is, if the business does more than one. Drives the check_before_sending list.
labourNoLabour lines. Give days OR hours (time on the job, per person) and the server prices it from the trade's saved rate; or give a fixed price in pounds. rate: trade (default, the trade's own rate) or labourer (their mate or apprentice rate). people: how many on site for that time. rate_override: a one-off day or hour rate in pounds.
depositNoOverride the trade's usual deposit rule for this quote only. Deposit rule. basis percent (with percent), fixed (with amount in pounds), materials (deposit equals the materials total), or none. no_deposit_under: no deposit on quotes below this total in pounds.
summaryNoTwo to four plain sentences describing the work as found on the visit, written for the customer. No jargon they would not understand.
customerYesWho the quote is for. type: homeowner, landlord, tenant, business (buying for itself) or contractor (a builder or main contractor buying your work). For business or contractor customers also give vat_registered, cis_registered and end_user, because they decide whether the construction domestic reverse charge applies.
discountNoOptional discount before VAT: percent OR amount (pounds), with a short reason the customer sees.
durationNoTime on site, for example "3 working days".
materialsNoMaterials. unit_cost is what the TRADE pays per unit in pounds; the server adds their markup. Set cost_includes_vat true if the price came from a receipt or shelf price including VAT (the server strips it for VAT registered trades). Give a saved code instead of description and unit_cost to use the price book. Prices used here are remembered for next time.
trade_keyYesThe trade's secret key from setup_trade (starts qbk_).
exclusionsNoWhat is NOT included in this job, one short sentence each. Added to the trade's standard exclusions.
from_quoteNoStart from this past quote. Fields you send replace that quote's fields; customer is required.
assumptionsNoWhat the price assumes, for example "Clear access to the loft".
site_addressNoJob address, if different from the customer's address.
validity_daysNoHow many days the prices hold. Defaults to the trade's setting (usually 30).
optional_extrasNoOptional upgrades the customer can tick when accepting (for example an EV charger, a smart thermostat, extra sockets). price in pounds before VAT. Up to 6. Not included in the main total.
remember_pricesNoDefault true: material prices used here go into the price book.
include_standard_exclusionsNoDefault true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, but the description adds substantial context beyond them: the server computes VAT including the construction domestic reverse charge, applies the deposit rule and validity, assigns a running quote number, and returns warnings plus a check_before_sending list. It also warns the result is a draft, which explains the non-destructive but non-idempotent profile.

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?

Front-loaded with the core action, and the return-value sentence earns its place because no output schema exists. It is dense but nearly every clause carries information; only the mid-sentence VAT enumeration duplicates what the schema's vat_category descriptions already spell out.

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 22-parameter mutation tool with nested objects and no output schema, the description covers both the input groupings and the full return shape (totals, margin view, warnings, check_before_sending, PDF and phone-page links). Nothing an agent needs in order to call it correctly or interpret the response 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 the schema already documents all 22 parameters in depth. The description summarises the same groupings (labour priced from the saved rate, materials at trade cost marked up, other costs, optional extras) but adds little syntax or meaning the schema does not already carry; baseline 3 applies.

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?

States a specific verb and resource — pricing a job into a quote — and immediately names the scope (post-site-visit, VAT-correct, deposit rule, running quote number). It distinguishes itself from finalise_quote by declaring the output is 'a DRAFT until finalise_quote', so an agent can tell the two apart without opening schemas.

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

Usage Guidelines4/5

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

Gives clear context ('after a site visit') and two explicit modes: save=false previews numbers without saving, and from_quote copies a past quote for a new customer. It routes finalisation to finalise_quote but does not mention revise_quote or get_quote as alternatives, so the exclusion set is incomplete.

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.