Skip to main content
Glama

Fipe API

list_years_by_fipe_code

Read-only

List the model years of a vehicle from its FIPE code.

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>",
      "fipe_code": "<fipe_code>"
    },
    "name": "list_years_by_fipe_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipe_codeYesFIPE code, for example 004278-1
referenceNoreference code from list_references; omit it for the latest month
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=false, and the description adds nothing beyond that safety profile. It says nothing about ordering of the returned years, whether results are paginated, or what a nonexistent FIPE code produces.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity means it conveys the bare minimum rather than layered context.

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?

An output schema exists, so return values need not be explained, and 100% schema coverage handles parameters. However, the description omits the sibling differentiation and the cross-tool dependency on 'list_references', leaving the agent to infer those from structured fields alone.

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%, so all three parameters (fipe_code, vehicle_type, reference) are already documented with formats and examples. The description only restates fipe_code and adds no meaning about the optional 'reference' parameter or its default behavior, 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 of a vehicle') plus the key input ('from its FIPE code'). It is clear what the tool returns, but it does not distinguish itself from the sibling 'list_model_years', which an agent may see as equivalent.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of how to choose between this tool and 'list_model_years'. The dependency on 'list_references' for the reference parameter is only implied by the schema, not stated in the description.

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