Skip to main content
Glama

Find cars

find_cars
Read-onlyIdempotent

Search new cars for lease or finance in California. Every car comes with its monthly payment before tax for the stated credit tier and a deal_url, a page where the buyer finishes personally.

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": "find_cars"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoBuyer California ZIP, sets the tax rate. Default 90210.
bodyNoBody style filter, for example SUV, Sedan, Truck.
fuelNoFuel filter, for example Gas, Hybrid, Electric.
langNoLanguage of the page behind deal_url. Default en.
makeNoMake, one of: Hyundai, Kia, Nissan, Chevrolet, Volkswagen, Mazda, Subaru, Genesis, Honda, Toyota, BMW, Mercedes-Benz, Audi, Lexus, Acura, INFINITI, GMC, Cadillac, Jeep, Ford, Volvo, Chrysler, Ram, Dodge, Buick, Porsche, McLaren.
modeNoDeal type. Default lease.
pageNoPage, up to 5. For more cars narrow the search.
modelNoExact model name, for example K5. Zero results return available_models.
searchNoFree text over make, model and trim.
credit_tierNoBuyer credit tier by score: t1 = Tier 1 · 740+, t2 = Tier 2 · 720-739, t3 = Tier 3 · 680-719, t4 = Tier 4 · 660-679, t5 = Tier 5 · 620-659, t6 = Tier 6 · <620. Payments are calculated for every tier in this list, so pass the buyer's own tier. If omitted, the calculation uses t1. A payment is final only for the tier you name, and the bank decides approval.
miles_per_yearNoLease miles per year. Default 10000.
due_at_signing_usdNoAmount due at signing in dollars. Default is the amount shown on the site for this car.
max_monthly_payment_usdNoMonthly budget in dollars, checked against the payment before tax that each car shows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / max_monthly_payment_usd / description
      Previous value: -"Monthly budget in dollars."New value: +"Monthly budget in dollars, checked against the payment before tax that each car shows."
  2. Changed1 schema field changed
    • changedInput schema / properties / make / description
      Previous value: -"Make, one of: Hyundai, Kia, Nissan, Chevrolet, Volkswagen, Mazda, Subaru, Genesis, Honda, Toyota, BMW, Mercedes-Benz, Audi, Lexus, Acura, INFINITI, GMC, Cadillac, Jeep, Ford, Volvo, Chrysler, Ram, Dodge, Buick."New value: +"Make, one of: Hyundai, Kia, Nissan, Chevrolet, Volkswagen, Mazda, Subaru, Genesis, Honda, Toyota, BMW, Mercedes-Benz, Audi, Lexus, Acura, INFINITI, GMC, Cadillac, Jeep, Ford, Volvo, Chrysler, Ram, Dodge, Buick, Porsche, McLaren."
  3. Changed1 schema field changed
    • changedInput schema / properties / make / description
      Previous value: -"Make, one of: Hyundai, Kia, Nissan, Chevrolet, Volkswagen, Mazda, Subaru, Genesis, Honda, Toyota, BMW, Mercedes-Benz, Audi, Lexus, Acura, INFINITI, GMC, Cadillac, Jeep, Ford, Volvo, Chrysler."New value: +"Make, one of: Hyundai, Kia, Nissan, Chevrolet, Volkswagen, Mazda, Subaru, Genesis, Honda, Toyota, BMW, Mercedes-Benz, Audi, Lexus, Acura, INFINITI, GMC, Cadillac, Jeep, Ford, Volvo, Chrysler, Ram, Dodge, Buick."
  4. Changed1 schema field changed
    • changedInput schema / properties / credit_tier / description
      Previous value: -"Buyer credit tier by score: t1 = Tier 1 · 740+, t2 = Tier 2 · 720-739, t3 = Tier 3 · 680-719, t4 = Tier 4 · 660-679, t5 = Tier 5 · 620-659, t6 = Tier 6 · <620. Default t1. Terms are final only for the stated tier."New value: +"Buyer credit tier by score: t1 = Tier 1 · 740+, t2 = Tier 2 · 720-739, t3 = Tier 3 · 680-719, t4 = Tier 4 · 660-679, t5 = Tier 5 · 620-659, t6 = Tier 6 · <620. Payments are calculated for every tier in this list, so pass the buyer's own tier. If omitted, the calculation uses t1. A payment is final only for the tier you name, and the bank decides approval."
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value beyond that: it discloses that every result carries a pre-tax monthly payment for the stated credit tier and a deal_url where the buyer completes the purchase personally, which tells the agent what it will get back and that the tool does not close the deal.

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?

Two tight sentences with the scope and the key output guarantee front-loaded. No filler or redundancy.

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 read-only search with no output schema, the description covers purpose, scope, and the shape of results (payment plus deal_url). It could say more about pagination or zero-result behavior, but the schema already handles those, so it is largely 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 description coverage is 100%, so the schema already documents all 13 parameters thoroughly, including enums and defaults. The description only echoes the credit-tier concept ('stated credit tier') and pre-tax payment framing, adding little beyond the schema, so 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?

States a specific verb and resource ('Search new cars for lease or finance') plus a geographic scope (California), which is enough to distinguish it from get_payment and how_to_buy. It stops short of explicitly naming those siblings, so it lands at 4 rather than 5.

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?

The description implies when to use it (shopping for lease/finance deals in California) but gives no explicit when-not guidance or routing to get_payment/how_to_buy. Usage is inferable but not spelled out.

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