Skip to main content
Glama

Get Shielded Deal Thread, Verified OTD Quote & Filtered Reply Status

get_deal_thread

Inspect the current state of a shielded proxy deal thread (or entire Buyer Shield Pass scoreboard), including physical lot verification answers, itemized Out-The-Door (OTD) quote, hidden add-on/markup warnings, filtered BDC auto-responder count vs. substantive human manager replies, pass_threads_digest across all cross-shopped VINs, 6-Digit Release Voucher state, and recommended next action.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deal_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idNoThe unique thread_id returned by start_shielded_inquiry (e.g., 'dth_...').
buyer_pass_idNoOptional Buyer Shield Pass ID ('bp_...') to resolve the pass status, scoreboard digest, or latest auto-dispatched thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / buyer_pass_id / description
      Previous value: -"Optional Buyer Shield Pass ID ('bp_...') to resolve the pass status or latest auto-dispatched thread."New value: +"Optional Buyer Shield Pass ID ('bp_...') to resolve the pass status, scoreboard digest, or latest auto-dispatched thread."
    • changedInput schema / required
      Previous value: -[
      -  "thread_id"
      -]New value: +[]
  2. Changed1 schema field changed
    • addedInput schema / properties / buyer_pass_id
      Added value: +{
      +  "description": "Optional Buyer Shield Pass ID ('bp_...') to resolve the pass status or latest auto-dispatched thread.",
      +  "type": "string"
      +}
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the returned payload in detail (verification answers, itemized OTD quote, markup warnings, responder filtering, digest, voucher state), which implies a read-only inspection. However it never states permissions/authorization for a shielded thread, side effects, or what happens when both optional parameters are omitted.

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?

A single sentence, front-loaded with the core action and scope, followed by an enumeration of returned artifacts. Dense with domain jargon, but every clause adds distinguishing information and nothing is redundant filler.

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?

Rich on what the tool returns, but for a tool with zero required parameters it should explain the default behavior when neither thread_id nor buyer_pass_id is given (scoreboard vs. error). The absence of an output schema makes this gap more consequential.

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 100%, so the schema already documents both parameters with examples ('dth_...', 'bp_...'). The description adds only the notion that buyer_pass_id resolves pass status/scoreboard/latest thread, without clarifying the precedence or default when neither is supplied.

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: "Inspect the current state of a shielded proxy deal thread (or entire Buyer Shield Pass scoreboard)". The dual-mode framing is clear enough to distinguish it from mutating siblings like burn_proxy_thread or accept_deal_and_reveal, though it never names an alternative explicitly.

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 only implied: the tool surfaces a "recommended next action" and thread_id is described as coming from start_shielded_inquiry, which hints at its place in the workflow. There is no explicit when-to-use/when-not-to-use statement and no routing to siblings such as get_lead_status.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources