Skip to main content
Glama

Australian Vehicle Recall

Search recalls

search_recalls

Search the Australian vehicle recall index by make, model, year and publication date. Returns summaries only — full text is get_recall's job. The index lists what this database holds, so an empty page is not a statement that a vehicle is free of recalls.

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

Input Schema

NameRequiredDescriptionDefault
makeNoManufacturer name, matched case-insensitively and exactly.
yearNoModel year; matches recalls whose year range includes it.
limitNoRows to return, clamped to between 1 and 20. Defaults to 20.
modelNoModel name; a case-insensitive substring, so `cresta` finds `Cresta 480`.
sinceNoOnly recalls published on or after this date, as `YYYY-MM-DD`.
cursorNoPass back the `next` value from the previous page; omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does good work: it discloses that only summaries are returned, that the result set is limited to what this index holds, and that empty results are not negative evidence. Pagination mechanics are left to the cursor field in the schema, which is a minor gap for an unannotated tool.

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?

Three short sentences, front-loaded with purpose, followed by return-shape and the caveat. No filler and every sentence carries information an agent needs.

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?

Covers purpose, scope limits, return shape, and the sibling handoff, which is sufficient for a six-parameter read-only search with fully documented params and no output schema. It stops short of describing what a summary contains or how paging terminates, but nothing essential to calling it correctly is missing.

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%, so every parameter (make, model, year, since, limit, cursor) is already documented with matching semantics like substring matching for model. The description only lists the filter dimensions, adding no syntax or behavior beyond the schema, so the baseline of 3 applies.

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 specific verb (search) and resource (Australian vehicle recall index) plus the filter dimensions, and explicitly contrasts with the sibling get_recall for full text. An agent can distinguish it from get_recall and the VIN lookups without opening a schema.

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?

Explicitly routes the agent to get_recall when full text is needed and warns that an empty page does not prove a vehicle is recall-free. It does not address when to prefer lookup_vin/lookup_vins over this search, so the guidance is clear but not exhaustive.

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