Skip to main content
Glama

Fipe API

list_model_years

Read-only

List the model years and fuel types of a model.

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": {
      "vehicle_type": "<vehicle_type>",
      "brand_code": "<brand_code>",
      "model_code": "<model_code>"
    },
    "name": "list_model_years"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceNoreference code from list_references; omit it for the latest month
brand_codeYesbrand code from list_brands, for example 59
model_codeYesmodel code from list_models, for example 5940
vehicle_typeYesvehicle type: cars, motorcycles or trucks

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/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 idempotentHint=false, so the safety profile is covered by structured data. The description adds only that both model years and fuel types are returned, and says nothing about rate limits, pagination, or what an empty result means. Useful but thin beyond the annotations.

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?

A single short sentence with no wasted wording and the resource front-loaded after the verb. It is efficient, though its brevity comes at the cost of the missing guidance noted elsewhere.

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?

With full schema coverage, an output schema, and annotations, the essentials for invocation are present. Still missing is any explanation of how the optional reference parameter interacts with the result set or how vehicle_type constrains the lookup, which matters for a 4-parameter tool with a temporal default.

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%, with each parameter documented in-schema, including the reference default of "latest month" and example codes. The description contributes no additional parameter meaning, so the baseline of 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: "List the model years and fuel types of a model." An agent can tell it retrieves year/fuel-type enumerations for a given model. However, it does not differentiate itself from the sibling list_years_by_fipe_code, which sounds like it serves an overlapping purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The presence of a near-duplicate sibling (list_years_by_fipe_code) makes the absence of routing guidance a real gap rather than a minor one.

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