Skip to main content
Glama

Fipe API

get_vehicle_by_fipe_code

Read-only

Get the FIPE price and the details of a vehicle from its FIPE code and year 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>",
      "year_code": "<year_code>"
    },
    "name": "get_vehicle_by_fipe_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipe_codeYesFIPE code, for example 004278-1
referenceNoreference code from list_references; omit it for the latest month
year_codeYesyear code from list_years_by_fipe_code, for example 2014-3
vehicle_typeYesvehicle type: cars, motorcycles or trucks

Output Schema

NameRequiredDescriptionDefault
fuelYes
brandYes
modelYes
priceNo
codeFipeYes
modelYearYesmodel year, 32000 means a new vehicle (zero km)
fuelAcronymYes
vehicleTypeYes1 is car, 2 is motorcycle, 3 is truck
priceHistoryNo
referenceMonthNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the retrieval nature is known and the description does not contradict it. The description adds nothing beyond annotations, however: it does not say what happens when the reference is omitted (latest month) or how the code lookup can fail, which would have been useful extra 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?

A single front-loaded sentence that names the returned data and the lookup keys with zero padding. Nothing is repeated or wasted.

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?

An output schema exists, so return values need no explanation, and all four parameters are documented in the schema. The only meaningful gap for an agent is routing against get_vehicle and get_vehicle_by_plate, which the description does not address.

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 format examples for fipe_code and year_code and an explanation of the optional reference parameter, so the schema carries the load. The description only echoes two of the four parameters and adds no syntax or default behavior beyond what structured data provides.

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: retrieve FIPE price and vehicle details keyed on FIPE code and year code. That is enough to separate it from list_* tools and from the plate-based lookup, though the description never names the sibling get_vehicle that likely overlaps in scope.

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 only implied by the required keys: call it when you already have a FIPE code and year code. There is no explicit when-to-use versus get_vehicle or get_vehicle_by_plate, and no note that codes should first come from list_years_by_fipe_code.

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