Skip to main content
Glama
Sign In

Nero Quote Builder

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Save materials to the price book

save_price_items
Idempotent

Add or update materials in the trade's price book, so later quotes can use { code, qty } and the cost, unit and markup fill in. Materials used in quotes are also remembered automatically.

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>",
      "price_items": "<price_items>"
    },
    "name": "save_price_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
trade_keyYesThe trade's secret key from setup_trade (starts qbk_).
price_itemsYesMaterials the trade buys often, saved to their price book. Each: code (short id, optional), description, unit, unit_cost (pounds, what they pay), cost_includes_vat, markup_percent (optional, overrides the default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare write, idempotent, non-destructive, closed-world behaviour, so the bar is lower. The description still adds real context beyond them: this is an upsert ('add or update'), the saved data feeds later quote pricing with code/qty/cost/unit/markup, and there is an automatic capture path when materials appear in quotes.

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?

Two sentences, front-loaded with the action and its benefit, with no filler. The clause 'the cost, unit and markup fill in' is slightly compressed and reads a little cryptically on first pass.

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?

For a two-parameter write tool with full annotation coverage and no output schema, the description covers purpose, upsert semantics, and downstream consumption adequately. What is missing is update-time behaviour (are omitted fields on an existing item preserved or blanked?) and any failure conditions such as an invalid trade_key.

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 100%, so trade_key (a qbk_ secret from setup_trade) and every price_items field are already documented in the schema. The description adds the useful framing that { code, qty } are the identifiers later quotes use, but does not clarify what is preserved versus overwritten when updating an existing item.

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?

The description gives a specific verb pair ('add or update') and resource ('materials in the trade's price book'), plus the downstream effect on quotes. It is clearly distinguishable from quote-oriented siblings like draft_quote or finalise_quote, though it never names a sibling explicitly.

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?

Usage is implied rather than stated: it should be called when a trade wants materials reusable in later quotes, and the closing line hints that materials already used in quotes are stored automatically, reducing the need to call this. There is no explicit when-to-use/when-not statement or named alternative.

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 toolsInspect
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.

Resources