Skip to main content
Glama
Sign In

Nero Quote Builder

by io.github.Nero-Engine
OverviewDiscussionsAdmin

List quotes

list_quotes
Read-onlyIdempotent

Recent quotes, newest first, with status (draft, sent, viewed, queried, accepted, declined, expired, withdrawn), total and whether there is news. Filter by status or search customer name, job title or number.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
statusNo
trade_keyYesThe trade's secret key from setup_trade (starts qbk_).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world and non-destructive behavior, so the bar is lower; the description adds genuinely new context by disclosing sort order, the fields returned per quote, and the full set of status values. It omits truncation/pagination behavior implied by the limit parameter, which keeps it from a 5.

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?

Two dense sentences, front-loaded with what is returned and then how to narrow it; the long status list earns its space because the schema has no enum to carry it.

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?

With no output schema and thin parameter coverage, the description does most of the work by describing return fields, ordering and filters. It never states the scope relationship to trade_key (that results are the quotes belonging to that trade) or what limit defaults to, which is a modest but real gap for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% (only trade_key documented), so the description must compensate, and it does: it clarifies that search matches customer name, job title or number, and enumerates the legal status values despite no enum being defined in the schema. The limit parameter is left unexplained, which is the remaining gap.

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 names the resource (quotes), the ordering (newest first), the returned fields (status, total, 'news' flag) and the filter dimensions, which is enough to distinguish it from get_quote or quote_activity. It stops short of an explicit 'this lists many quotes for one trade' framing, but the purpose is unambiguous.

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: 'Recent quotes, newest first' plus filter options signals a browsing/listing scenario, but there is no explicit when-to-use, no mention of when to prefer get_quote for a single record, and no guidance on how status/search interact.

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