autoria-mcp

list_generations

Retrieve car model generations with production years, including current models indicated by yearTo as 0.

Instructions

List generations for a model. Cached 7 days.

Raw upstream shape (camelCase: generationId, yearFrom, yearTo). Note yearTo: 0 is a sentinel for "current / still produced", not a literal year.

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": {
      "model_id": "<model_id>"
    },
    "name": "list_generations"
  }
}

Input Schema

Name	Required	Description	Default
`model_id`	Yes	Model id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Jul 30, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses caching duration (7 days) and the raw upstream shape (camelCase fields) with a special note about yearTo: 0 as a sentinel, adding significant behavioral context.

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?

The description is concise, using only two sentences and a note. Every sentence provides essential information without redundancy.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers caching, field names, and sentinel behavior. It lacks mention of pagination or result limits, but these are minor omissions.

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% with one parameter (model_id) described as 'Model id.' The description does not add additional meaning beyond what the schema already provides.

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?

The description clearly states 'List generations for a model', specifying the verb (list) and resource (generations for a model), which distinguishes it from sibling tools like list_colors or list_modifications.

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 implies using this tool when needing generations for a model, but it does not provide explicit when-to-use or when-not-to-use guidance or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.