Skip to main content
Glama
Sign In

Nero Quote Builder

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Answer a customer question on the quote page

reply_to_customer

Answer a customer's question. The answer shows on their quote page under their question. Price or scope changes are made with revise_quote, not here.

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>",
      "message": "<message>"
    },
    "name": "reply_to_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteYesQuote number, for example BLE-0007.
messageYes
trade_keyYesThe trade's secret key from setup_trade (starts qbk_).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the description's job is to add consequence detail. It does: the answer becomes visible to the customer on their quote page under the question, which is the key side effect an agent needs. It does not say whether the customer is notified, whether a reply can be edited or removed, or whether repeated sends stack — modest gaps for a customer-facing write.

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?

Three short sentences, front-loaded with the action and the visible effect, ending with the exclusion. No restatement of the title, no filler, nothing that could be cut without losing information.

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 three-parameter, non-destructive write with no output schema, the definition covers purpose, customer-visible effect, and the nearest competing tool. Residual gaps are around notification behavior and post-send editability, which are minor relative to the tool's simplicity.

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 67%; quote and trade_key are documented in-schema (with an example number and the qbk_ prefix), while 'message' has no schema description. The description partially compensates by explaining that the message text is what appears under the customer's question, but it adds no format, length, or content constraints. That is baseline adequacy rather than added depth.

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 states a specific verb and resource ('Answer a customer's question') and immediately scopes the effect ('shows on their quote page under their question'). It also names the sibling it is not (revise_quote), so an agent can separate messaging from quote mutation without opening either 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?

It gives an explicit when-not rule with the correct alternative: price or scope changes go to revise_quote, 'not here'. What is missing is positive framing for adjacent needs — e.g. reading a quote or its history — but the boundary that matters most for this tool is stated outright.

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