Skip to main content
Glama

Send Shielded Out-The-Door Counter-Offer to Dealership

send_counter_offer

Send a firm, structured Out-The-Door (OTD) counter-offer (and optionally stipulate removal of mandatory dealer add-ons) on an active proxy thread while keeping the buyer's real phone and email completely hidden.

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": {
      "thread_id": "<thread_id>",
      "target_otd_usd": "<target_otd_usd>"
    },
    "name": "send_counter_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional negotiation context (e.g., competing dealership OTD quote to beat).
thread_idYesActive proxy deal thread_id.
auto_negotiateNoOptional toggle to enable or disable autonomous multi-round Agent Playbook counter-offers on subsequent dealer replies.
financing_typeNoOptional updated payment/financing method.
target_otd_usdYesFirm all-in Out-The-Door counter-offer in whole USD (including tax, tag, and doc fee).
max_auto_roundsNoOptional max autonomous rounds (1-5).
ready_to_sign_byNoCommitment window if counter-offer is approved in writing (e.g., 'Tomorrow before 4 PM').
walk_away_otd_usdNoOptional updated buyer walk-away Out-The-Door ceiling in whole USD for autonomous follow-up rounds.
cross_shop_leverageNoOptional toggle to cite lower verified OTD quotes from competing threads on the same pass.
remove_mandatory_addonsNoIf true (default), stipulates removal of dealer-installed add-ons/protection packages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / auto_negotiate
      Added value: +{
      +  "description": "Optional toggle to enable or disable autonomous multi-round Agent Playbook counter-offers on subsequent dealer replies.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / cross_shop_leverage
      Added value: +{
      +  "description": "Optional toggle to cite lower verified OTD quotes from competing threads on the same pass.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / max_auto_rounds
      Added value: +{
      +  "description": "Optional max autonomous rounds (1-5).",
      +  "type": "integer"
      +}
    • addedInput schema / properties / walk_away_otd_usd
      Added value: +{
      +  "description": "Optional updated buyer walk-away Out-The-Door ceiling in whole USD for autonomous follow-up rounds.",
      +  "type": "integer"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does add genuinely useful context the schema cannot: the buyer's real phone and email stay completely hidden, and dealer add-on removal can be stipulated. However, it omits whether sending is irreversible, whether the offer is binding on the buyer, that auto_negotiate spawns autonomous multi-round replies, and what happens if the thread is inactive or burned.

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 the core action first and the privacy guarantee second; no filler or repetition. It is dense but readable, though 'firm, structured' leans slightly promotional and the sentence becomes long with the parenthetical clause.

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?

Ten parameters, no output schema, and no annotations make this a complex mutation tool, yet the description says nothing about the outcome of a send (does it return a thread message, an acknowledgment, a new state?) or how the autonomous negotiation toggles interrelate. Adequate for understanding what it does, thin for understanding what follows.

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 every parameter (including auto_negotiate, max_auto_rounds, walk_away_otd_usd, cross_shop_leverage) is already documented in the schema. The description reinforces only two semantics — that the OTD figure is 'firm' and that add-on removal is an option — and adds no interpretation beyond that. 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 description names a specific verb (send) and resource (an Out-The-Door counter-offer) and pins down the channel ('on an active proxy thread'), which implicitly distinguishes it from siblings like start_shielded_inquiry (creates a thread) or accept_deal_and_reveal (closes one). It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 by the phrase 'on an active proxy thread' — the agent can infer the thread must already exist and be live. There is no explicit when-to-use vs. when-not (e.g., burned threads, already-accepted deals), no stated prerequisites, and no pointer to get_deal_thread for checking thread state before countering.

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