Skip to main content
Glama

Australian Vehicle Recall

Look up a VIN

lookup_vin

Look up an Australian vehicle recall by VIN. status: "recalled" means the VIN appears in the manufacturer's published recall list, with matches. status: "no_record" means this database holds no record for that VIN. There is no "not recalled" answer: a VIN we do not hold is not a vehicle free of recalls.

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": {
      "vin": "<vin>"
    },
    "name": "lookup_vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesThe 17-character VIN to look up. Case-insensitive; VINs never contain I, O or Q.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 real work: it defines the two possible status values and explicitly warns there is no 'not recalled' answer. That negative-result caveat is exactly the kind of behavior an agent would otherwise misread. It stops short of stating read-only safety or error behavior for malformed VINs, so not 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?

Three tight sentences, front-loaded with the action, then the result semantics. Every sentence carries information; only mild redundancy between the 'no_record' definition and the closing caveat.

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, so the description must explain return values, and it does cover status and the matches field. It does not describe the shape of individual match entries, leaving a small gap for a tool with no output schema.

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 vin parameter is fully documented, including length and forbidden characters. The description adds no syntax or format guidance beyond the schema, so the 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: look up an Australian vehicle recall by VIN. The scope (Australian recalls) is precise, but nothing distinguishes it from the sibling lookup_vins, which an agent would reasonably read as a batch variant of the same lookup.

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?

Usage is implied by the single-VIN framing, but there is no explicit statement of when to prefer this over lookup_vins (many VINs) or get_recall. The agent must infer the routing from the tool name alone.

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