Skip to main content
Glama

Fipe API

get_vehicle

Read-only

Get the FIPE price and the details of a vehicle from its brand, model and year codes.

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>",
      "year_code": "<year_code>"
    },
    "name": "get_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceNoreference code from list_references; omit it for the latest month
year_codeYesyear code from list_model_years, for example 2014-3
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
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

B3.4/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 safety and external-data sourcing are covered. The description adds only that the result includes a FIPE price plus vehicle details, and says nothing about the price being reference-month dependent despite idempotentHint=false, which is the one behavioral trait worth explaining.

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; the purpose and the identity key arrive first. The word 'details' is the only vague element in an otherwise efficient line.

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 described, and annotations cover the safety profile. Still, for a tool with four required codes the description gives no hint of the required lookup chain or that price results are tied to a reference month.

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 five parameters, including the optional 'reference' and the enumerate-it-yourself vehicle_type, are already documented with examples. The description only repeats brand/model/year codes and omits 'reference' and 'vehicle_type' entirely, adding no meaning beyond the schema.

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 ('Get') and resources ('FIPE price and the details of a vehicle'), and pins the lookup key to brand/model/year codes, which implicitly separates it from get_vehicle_by_fipe_code and get_vehicle_by_plate. It stops short of naming those siblings, so differentiation requires a small inference.

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 lookup key implies when this tool applies (you have brand/model/year codes, not a plate or FIPE code), but the description never states that explicitly or points to an alternative. Prerequisite calls (list_brands, list_models, list_model_years) are only implied via the schema's parameter descriptions, not the tool 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