Skip to main content
Glama

Fipe API

get_price_history

Read-only

Get the FIPE price history of a vehicle from its FIPE code and year code. Requires a paid subscription token.

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_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipe_codeYesFIPE code, for example 004278-1
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds a genuinely useful operational constraint the annotations do not cover: 'Requires a paid subscription token.' It does not explain why the call is marked non-idempotent or whether history is paginated, leaving some behavioral gaps.

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?

Two sentences, both front-loaded and free of filler: the first identifies the resource and its inputs, the second flags the subscription requirement before the agent attempts a call.

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?

For a simple three-parameter read tool with full schema coverage and an output schema covering return values, the definition is nearly complete. The remaining gap is guidance on when to prefer this over sibling vehicle-lookup tools.

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% and all three parameters carry examples and enum-like guidance, so the schema does the heavy lifting. The description only restates that a FIPE code and year code are needed, adding no format or validation detail 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?

The description states a specific verb and resource: 'Get the FIPE price history of a vehicle,' which is distinguishable from siblings like get_vehicle_by_fipe_code because it names price history rather than vehicle attributes. It does not explicitly call out the sibling it differs from, keeping it just below a 5.

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 phrase 'from its FIPE code and year code' implies you must already have those identifiers (obtained via the list_* tools), but there is no explicit when-to-use statement or comparison against get_vehicle_by_fipe_code. Usage is inferable rather than stated.

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