QuoteBuild

Get quote

get_quote

Read-only

Gets one owned quote and its recipient-visible pack data.

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": {
      "quoteId": "<quoteId>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description	Default
`quoteId`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No
`warnings`	Yes
`provenance`	No
`assumptions`	Yes
`nextActions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two genuine nuggets beyond that: the 'owned' access scoping (you only get quotes you own) and that the returned pack data is the 'recipient-visible' subset rather than the full record. It says nothing about failure behavior for a missing or non-owned quoteId, which is the main remaining gap.

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 front-loaded sentence with no filler; the access scope and return scope are packed efficiently. The term 'pack data' is domain jargon that costs a little clarity for an outside agent.

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?

An output schema exists, so return-value detail is not required, and annotations cover the safety profile. However, for a fetch-by-id tool the definition leaves the identifier's origin and the not-found/not-owned outcome unspecified, which an agent calling it cold would need.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions the sole parameter, its format, or where a quoteId is obtained (e.g. from a list or create call). 'One owned quote' only loosely implies lookup by identifier, so the description does not compensate for the undocumented schema.

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?

States a specific verb and resource ('Gets one owned quote') plus the scope of data returned ('its recipient-visible pack data'), which is enough for an agent to distinguish a single-record quote fetch from the create/send/prepare quote siblings. It stops short of naming a contrasting sibling (e.g. get_estimate) so the quote-vs-estimate boundary is left implicit.

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?

There is no when-to-use or when-not-to-use language, no prerequisites, and no alternative named. The only hint is the word 'one', which weakly implies single-record lookup by identifier, but an agent must infer that retrieval rather than listing is intended.

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

All QuoteBuild 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.

Resources

Need Help?