Skip to main content
Glama
Sign In

Nero Quote Builder

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Show one quote in full

get_quote
Read-onlyIdempotent

One quote in full: lines, totals, VAT working with HMRC sources, margins (trade only), the customer's answer, history (drafted, sent, opened, accepted) and links.

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": "get_quote"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful disclosure about what is returned (VAT working with HMRC sources, trade-only margins, customer answer, lifecycle history), which partly substitutes for the absent output schema, but says nothing about error behavior for a wrong quote number or invalid trade_key.

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?

A single compact sentence that front-loads 'One quote in full' before enumerating payload sections; every clause earns its place. It is a noun-phrase fragment rather than a complete statement, which slightly weakens the framing.

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 simple two-parameter read tool with no output schema, the description adequately enumerates what comes back, including a notable conditional (margins visible only for trades). The main residual gap is the absence of usage guidance relative to the many quote-related siblings.

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%, with both quote (format example BLE-0007) and trade_key (qbk_ prefix from setup_trade) documented in the schema. The description adds no meaning beyond that, so the 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?

The phrase 'One quote in full' plus the enumerated payload (lines, totals, VAT, margins, customer answer, history, links) makes clear this retrieves a single quote's complete record, distinguishable from list_quotes and quote_activity. It lacks an explicit verb such as 'retrieve' or 'show', but the resource and scope are unambiguous.

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?

No guidance on when to choose this over siblings like list_quotes (browse), quote_activity (activity only), or get_trade. There are no stated prerequisites or exclusions; the only signal is the implicit 'one quote' vs. list distinction.

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