Nero Quote Builder

Change or withdraw a quote

revise_quote

Destructive

Change a quote. Send only the fields that change (a list you send, such as materials, replaces that whole list). A draft stays a draft. A quote the customer already has becomes the next revision on the same link, with fresh dates, and any earlier answer is cleared. Accepted quotes cannot change. status "withdrawn" pulls a quote. use_current_settings true re-prices with the trade's latest rates.

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>",
      "quote": "<quote>"
    },
    "name": "revise_quote"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Anything else the customer should read.
`other`	No	Other 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).
`quote`	Yes	Quote number, for example BLE-0007.
`start`	No	Likely start, for example "w/c 7 December".
`title`	No	Short job name the customer sees, for example "Full rewire, 3 bedroom semi" or "Replace combi boiler".
`trade`	No	Which trade this job is, if the business does more than one. Drives the check_before_sending list.
`labour`	No	Labour 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.
`reason`	No
`status`	No
`deposit`	No	Override 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.
`summary`	No	Two to four plain sentences describing the work as found on the visit, written for the customer. No jargon they would not understand.
`customer`	No	Who 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.
`discount`	No	Optional discount before VAT: percent OR amount (pounds), with a short reason the customer sees.
`duration`	No	Time on site, for example "3 working days".
`materials`	No	Materials. 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_key`	Yes	The trade's secret key from setup_trade (starts qbk_).
`exclusions`	No	What is NOT included in this job, one short sentence each. Added to the trade's standard exclusions.
`assumptions`	No	What the price assumes, for example "Clear access to the loft".
`site_address`	No	Job address, if different from the customer's address.
`validity_days`	No	How many days the prices hold. Defaults to the trade's setting (usually 30).
`optional_extras`	No	Optional 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_prices`	No
`use_current_settings`	No
`include_standard_exclusions`	No	Default true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing mutation side effects the agent could not otherwise predict: a sent quote becomes the next revision on the same link with fresh dates, any earlier customer answer is cleared, and use_current_settings re-prices at latest rates. The annotations already flag destructiveHint=true, and the description is consistent with that, but it does not say what the response contains after the revision is created.

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?

Very short and front-loaded: the core change semantics come first, state rules next, parameter notes last. The telegraphic fragments ("status \"withdrawn\" pulls a quote", "use_current_settings true re-prices...") are dense but each sentence carries distinct information, with no filler.

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?

For a 24-parameter mutation with nested objects and no output schema, the description covers state transitions well but leaves the return value entirely unexplained — an agent cannot tell whether the call returns the new revision number, updated totals, or nothing. It also omits the auth requirement (trade_key) and says nothing about which fields are illegal once a quote is accepted.

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 coverage is high (83%), so the baseline is 3. The description does add real semantics for two fields — list parameters replace the whole list rather than append, and use_current_settings triggers re-pricing — but the other 22 parameters, including the large nested customer, labour, materials and deposit objects, get no meaning from the description beyond what the schema already says.

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 ("Change a quote") and then immediately disambiguates the near-siblings by lifecycle state: a draft stays a draft, a sent quote becomes the next revision on the same link, an accepted quote cannot change. An agent can tell this apart from draft_quote and finalise_quote without opening any schema.

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 a clear when-to-use rule (send only the fields that change) and an explicit exclusion (accepted quotes cannot change), plus a named escape hatch for cancellation (status "withdrawn"). It never names an alternative tool to use instead when the quote is still a draft or already accepted, so routing in those edge cases is left to inference.

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

All Nero Quote Builder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.