Skip to main content
Glama

Load nearby choices

see_car_choices_options
Read-only

The Configure card calls this tool to load the next steps. The assistant does not call it.

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": {
      "make": "<make>",
      "model": "<model>",
      "year": "<year>",
      "zip": "<zip>"
    },
    "name": "see_car_choices_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesThe buyer's five-digit ZIP code.
fuelNoA fuel type.
makeYesThe make.
trimNoA trim.
yearYesThe model year.
modelYesThe model.
radiusNoMiles from the ZIP code, from 1 to 100.
drivetrainNoA drivetrain.
exteriorColorNoAn exterior color.
interiorColorNoAn interior color.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds the non-obvious behavioral fact that invocation is driven by an external UI card rather than the model. Beyond that it discloses nothing about what is returned, whether results are paginated or limited, or what happens with the optional filter parameters. With no output schema, that leaves real behavioral gaps.

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?

Two short sentences with no filler, and the routing constraint that matters most is stated directly. The phrasing "load the next steps" is imprecise rather than bloated, so the issue is under-specification, not verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with ten parameters, four required, no output schema, and filter semantics that matter (radius bounds, optional narrowing fields), the description explains almost nothing an agent would need if it ever had to reason about this tool's results. It is adequate only as a routing instruction, which may be all that was intended, but it is thin relative to the tool's surface area.

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 all ten parameters (make, model, year, zip, trim, fuel, radius, drivetrain, colors) are documented in the schema, establishing the baseline of 3. The description adds no meaning about how the filters combine, defaults, or whether radius defaults when omitted. Enum-free fields like fuel and drivetrain also carry no description-level guidance on accepted values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the tool loads "the next steps," which is a vague restatement of the title "Load nearby choices" and never states what is actually loaded (car choices/options) or in what form. Its one substantive contribution is naming the caller (the Configure card), which tells an agent this is a UI-driven step rather than a general-purpose lookup, but that is routing information rather than a clear verb+resource statement.

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?

It gives an explicit, unambiguous when-NOT rule: "The assistant does not call it," and names who does call it (the Configure card). That is stronger exclusion guidance than most definitions provide. It stops short of a 5 because it names no alternative tool the assistant should use for nearby car choices, even though siblings like see_car_choices and see_cars_near_buyer exist.

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