Skip to main content
Glama

Preview the request

requests_preview
Read-only

Shows what requests_submit would do, and contacts no dealership. It also shows what a new-car request would do, after see_car_choices. It returns the request as given, what happens next, and a previewToken that works for 15 minutes, for this exact request and idempotencyKey only. requests_submit takes this previewToken.

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": {
      "idempotencyKey": "<idempotencyKey>",
      "zip": "<zip>"
    },
    "name": "requests_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesThe buyer's five-digit US ZIP code, as the buyer gave it. The request goes to dealerships near this ZIP. Do not guess it.
limitNoHow many dealerships the buyer wants Ridekick to contact, at most 5.
replacesNoThe previewToken that expired for this same request. The answer then carries `sameFacts` and `silentOk`. When `silentOk` is true, the buyer's earlier yes still covers this request and the new `previewToken` can be sent with the same `idempotencyKey` as before.
consentIdNoThe id of the consent words the card drew for this tap. Sent only by the card.
listingIdNoOptional. The car the buyer chose: the listingId from see_cars_near_buyer, or the reference after "Ridekick reference: " in the buyer's message, such as 7K4M-2QPX, as written. Sent with zip, and without configuration, radiusMiles, limit or acceptFewer. Valid for 24 hours for this buyer. A car found by a new search has a new listingId, and a new listingId comes with a new idempotencyKey.
acceptFewerNoFalse: if fewer dealerships match than the limit, nothing is sent and you are told. True: go ahead with the fewer.
radiusMilesNoHow far from the buyer's ZIP code to look for dealerships, in miles.
configurationNoThe car the buyer asked about and confirmed. Sent instead of listingId. The request names the car with these fields as given. Use only what the buyer told you; do not guess a field.
paymentMethodNoOptional. How the buyer said they plan to pay: cash, finance, lease, or not_sure. Ridekick stores it with the request.
idempotencyKeyYesA key you make up for this one request. The same key sent again with the same request never sends it twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / paymentMethod
      Added value: +{
      +  "description": "Optional. How the buyer said they plan to pay: cash, finance, lease, or not_sure. Ridekick stores it with the request.",
      +  "enum": [
      +    "cash",
      +    "finance",
      +    "lease",
      +    "not_sure"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds real value by confirming no dealership is contacted and by disclosing the 15-minute token lifetime, its binding to this exact request and `idempotencyKey`, and that the response carries the request as given plus what happens next. That is substantive behavior beyond the structured fields. A slightly fuller account of what the preview does when it cannot satisfy the request would push this to a 5.

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?

Four tight sentences, front-loaded with the core distinction from `requests_submit` before the return-value and token details. No filler, though the token-lifetime sentence packs several constraints into one run-on that takes a second read.

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?

With 10 parameters, a nested `configuration` object and no output schema, the description compensates by naming the three things the response contains, including the token the agent must carry forward. Combined with the exhaustive schema coverage, an agent has what it needs; only edge-case behavior under unsatisfiable requests is left unstated.

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% and the parameter docs are unusually rich, including the `replaces`/`silentOk` expiration path and the `listingId` versus `configuration` exclusivity. The description adds only the linkage between the `previewToken` and the `idempotencyKey` scope, which is not an input parameter itself, so it earns the baseline rather than more.

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 concrete verb and resource — it previews what `requests_submit` would do without contacting a dealership — and draws the line against the sibling that actually submits. The follow-up sentence about the new-car path after `see_car_choices` removes any ambiguity about which request shapes it accepts.

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 relationship to `requests_submit` is explicit: this is the dry run, and the submit tool consumes the `previewToken`. The `see_car_choices` pointer tells the agent where a new-car request comes from. It never explicitly says "call this before submitting" as a rule, but the surrounding context makes the ordering clear enough.

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