Skip to main content
Glama

Australian Vehicle Recall

Look up several VINs

lookup_vins

Look up a batch of Australian vehicle recalls by VIN. Each result carries status: "recalled" with matches, or status: "no_record". There is no "not recalled" answer: a VIN we do not hold is not a vehicle free of recalls. One invalid VIN is reported in its own result instead of failing the batch.

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": {
      "vins": "<vins>"
    },
    "name": "lookup_vins"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinsYesVINs to look up, in the order answers should come back. At most 10 per call. Case-insensitive; a VIN is 17 characters and never contains I, O or Q.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the two possible result statuses, the critical caveat that absence of a record is not evidence of no recall, and per-VIN error containment rather than whole-batch failure. It omits any note on auth, rate limits, or what `matches` contains, but the core behavioral contract is clear.

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?

Four short sentences, front-loaded with purpose, then the result contract, then the interpretive caveat, then error behavior. Nothing is redundant and each sentence carries a distinct, actionable point.

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?

There is no output schema, and the description steps in to describe the return shape (`status: "recalled"` with `matches`, or `no_record`) along with per-VIN error behavior. What remains unstated — pagination, rate limits, contents of `matches` — is minor for a bounded 10-VIN batch read tool.

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 100% and the single `vins` parameter already documents ordering, the 10-per-call cap, and VIN format rules. The description adds only an indirect hint that results correspond per-VIN, so it neither compensates for nor duplicates the schema meaningfully — 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 with batch scope ("Look up a batch of Australian vehicle recalls by VIN"), which distinguishes it from a singular lookup. It never names the sibling lookup_vin as the single-VIN alternative, so the differentiation is only implied by the word "batch".

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 clarifies interpretation ("There is no 'not recalled' answer") and error tolerance ("One invalid VIN is reported in its own result instead of failing the batch"), which is real usage context. But it gives no explicit when-to-use-this vs lookup_vin or get_recall guidance, leaving routing to inference from sibling names.

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