Skip to main content
Glama

J.C. Lewis Auto Group

build_proposal

Build a priced deal proposal for a specific vehicle and customer. Returns the full proposal payload for the widget to render: vehicle details with photo, deal breakdown (selling price, Georgia TAVT, fees, final price), and a finance grid of monthly payments across terms and down payments. Pricing starts from our published internet price. If the customer says the price is too high, call again with negotiation_round=2 for our best offer (2% off) — there is NO third round; if they still decline, call submit_deal_handoff so a salesperson can work the deal. ALWAYS ask what state the customer will register the vehicle in and pass buyer_state (two-letter code): Georgia buyers get Georgia TAVT, title, and tag, while out-of-state buyers get a proposal that EXCLUDES tax, title, and registration (owed in their home state and not calculated here) — say so plainly and never invent another state's tax rate. Payments are ESTIMATES based on market-average rates for the given credit tier, not approvals — always present them that way and never promise a rate or approval. Optional: terms (default 48/60/72), down_payments (default 0/1000/2000), credit_tier (750+, 700-749, 650-699, 600-649).

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": {
      "vin": "<vin>",
      "customer_name": "<customer_name>"
    },
    "name": "build_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes
termsNo
buyer_stateNo
credit_tierNo700-749
customer_nameYes
down_paymentsNo
customer_emailNo
customer_phoneNo
apply_incentivesNo
salesperson_nameNo
negotiation_roundNo
salesperson_emailNo
salesperson_phoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description fully carries the burden: it discloses the pricing basis (published internet price), the exact 2% best-offer ceiling, that payments are market-average estimates and not approvals, and that out-of-state proposals intentionally exclude tax/title/registration. These are behavioral facts an agent could not infer from the schema alone.

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?

Front-loads purpose and return payload, then negotiation policy, then state handling, then optional parameters — a sensible order. It is long and leans on capitalized emphasis, but nearly every sentence carries operational content; only the deal-breakdown enumeration could be tightened.

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?

For a 13-parameter, no-output-schema tool, the description explains the return shape and the pricing/estimate semantics well. It omits failure modes (bad VIN, vehicle not in inventory) and whether the proposal is persisted, plus the contact/salesperson fields, which keeps it short of complete.

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 0%, so the description must compensate and it does for vin, buyer_state, negotiation_round, terms, down_payments, and credit_tier, including defaults and the allowed credit-tier buckets. However customer_email, customer_phone, apply_incentives, and the three salesperson_* fields get no explanation at all, leaving roughly half the parameters semantically bare.

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?

States a specific verb and resource — 'Build a priced deal proposal for a specific vehicle and customer' — and enumerates the returned payload (vehicle details, deal breakdown with Georgia TAVT, finance grid). An agent can distinguish this from submit_deal_handoff and quote-style siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: call again with negotiation_round=2 when the customer objects to price, no third round, escalate to submit_deal_handoff on continued decline. It also mandates asking for the registration state, which is a usage prerequisite rather than just a field note.

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