Skip to main content
Glama

lookup_recalls

Read-only

Look up recalls for a vehicle. Provide either a VIN or make/model/year.

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

Input Schema

NameRequiredDescriptionDefault
vinNoVIN to look up recalls for
makeNoVehicle make (e.g. Honda)
yearNoModel year (e.g. 2020)
modelNoVehicle model (e.g. Civic)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a small amount of behavioural context by noting the two lookup paths, but says nothing about data freshness, coverage, or relative reliability of VIN versus make/model/year lookups.

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 short sentences, zero filler, with the core action front-loaded and the input constraint immediately following. Nothing could be cut without losing information.

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?

For a low-complexity read-only lookup with full schema coverage and no output schema, the definition is adequate but leaves open what a recall record contains and how ambiguous make/model/year input is handled. Given the tool's simplicity this is a modest gap rather than a serious one.

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 four parameters (vin, make, model, year) are already documented with examples in the schema. The description only restates that VIN and make/model/year are alternatives; it adds no detail on partial matching, required combinations, or year format. Baseline 3 is appropriate.

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 gives a specific verb and resource ("Look up recalls for a vehicle") and names the two lookup modes, so an agent knows immediately what it returns. It does not distinguish itself from near-neighbours such as vin_recall_status or defect_investigations, so it stops short of a 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 second sentence is input guidance rather than usage guidance: it says to supply either a VIN or make/model/year. There is no statement of when to prefer this tool over vin_recall_status or defect_investigations, and no prerequisites or fallback behaviour are given.

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.