agent-ready-kit

Refine an existing quote

refine_quote

Use this when the user has shared additional context (organization type, compliance requirements, geography) after an initial request_quote. Tightens the quote band by re-running the engine with the merged context. Pass the quote_id from the original quote.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "refine_quote"
  }
}

Input Schema

Name	Required	Description
`quote_id`	Yes
`display_currency`	No	Optional ISO 4217 currency for displayed prices.
`additional_context`	No
`additional_constraints`	No

Output Schema

Name	Required	Description
`quote`	No
`status`	No
`message`	No
`quote_id`	No
`valid_until`	No
`tiered_offer`	No
`verification`	No
`genre_context`	No
`needs_new_quote`	No	True when the referenced quote expired — the agent should call request_quote to open a fresh one instead of treating this as a hard failure.
`message_for_user`	No	Plain-language summary the calling agent can render to its end user. Never includes sales-pressure language.
`next_step_options`	No
`narrowing_questions`	No
`needs_continuity_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The description mentions 'tightens the quote band' and 're-runs the engine', indicating a modification action. Annotations show non-read-only and non-destructive, which aligns. However, it does not describe whether the original quote is updated or a new one is created, or if there are any side effects (e.g., idempotency).

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?

The description is concise (2 sentences) and front-loaded with the usage trigger. However, it could be more structured by briefly listing key parameters. Still, it is efficient and avoids verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters including nested objects and a output schema, the description is insufficient. It omits explanations for the additional context and constraints parameters, which are crucial for correct invocation. The agent would need more detail to use the tool effectively.

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?

With schema description coverage at only 25%, the description should compensate but does not. Only quote_id is mentioned; the additional_context and additional_constraints parameters, which have complex nested structures, are not explained. The description adds little meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is for refining an existing quote after receiving additional context, with a specific verb ('refine') and resource ('quote'). It distinguishes from the sibling tool 'request_quote' by specifying it is for an existing quote with merged context.

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?

The description explicitly specifies when to use the tool: 'when the user has shared additional context... after an initial request_quote'. It also provides guidance on passing the quote_id, ensuring proper invocation. However, it does not explicitly state when not to use it or mention alternatives.

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

All agent-ready-kit tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.