Skip to main content
Glama

Brazilian FIPE reference price for one car: brand, model

auto_fipe_brazil_vehicle_prices
Read-only

Brazilian FIPE reference price for one car: brand, model, model year, fuel, FIPE code and reference month, from the public FIPE API. Needs the FIPE brand, model and year codes (numbers and a 'year-fuel' code); lookup lists are at /cars/brands. Reference prices are not a sale offer. Related tools on this server, for a different need: auto_carsdirect_vehicle when you need CarsDirect used-car listings near a US ZIP code: vehicle; auto_nhtsa_vehicle_complaints when you need US NHTSA owner-filed vehicle complaints for a make, model. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "brand": "<brand>",
      "model": "<model>",
      "year": "<year>"
    },
    "name": "auto_fipe_brazil_vehicle_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFIPE year code like 1985-1 (year and fuel code)
brandYesFIPE brand code, digits only (e.g. 21 = Fiat)
modelYesFIPE model code, digits only (e.g. 437)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's extra contribution is what matters: it discloses the billing model ($0.002 per successful call via x402 in USDC, failed calls not charged) and a semantic caveat that reference prices are not a sale offer. That is genuinely useful context an agent would otherwise have to discover by incurring cost, though it says nothing about rate limits or what happens on an invalid code.

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?

It is front-loaded with purpose, then prerequisites, then sibling routing, then cost — a sensible order for an agent to read. Sentences are dense but each carries information; the payment sentence is the most padded part ('USDC on Base, Solana and 10 more networks') and could be trimmed without losing meaning.

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?

With an output schema present, the description rightly does not describe return fields, and annotations plus the schema cover parameters. It adds cost, data source, prerequisite lookup location and a pricing caveat, which is complete enough for correct invocation; only failure/error behavior for bad codes is left unstated.

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 each of the three parameters is documented inline with format hints (digits-only brand/model, 'year-fuel' code like 1985-1), which sets the baseline at 3. The description adds only the provenance point that these codes must be looked up via /cars/brands; it repeats rather than deepens what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource (retrieve the Brazilian FIPE reference price for one car) and enumerates exactly which fields come back: brand, model, model year, fuel, FIPE code and reference month. It also names its source of truth (public FIPE API), which lets an agent distinguish it from the sibling listing/complaint tools without opening any schema.

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

Usage Guidelines4/5

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

It explains the prerequisite to calling it (you must already hold FIPE brand/model/year codes) and points to /cars/brands for lookups, then routes to alternatives by condition: auto_carsdirect_vehicle for US ZIP used-car listings and auto_nhtsa_vehicle_complaints for US owner complaints. What is missing is a 'when not to use' case for the tool itself, e.g. behavior when a vehicle is not in FIPE or when only a name is known, so it lands just short of a 5.

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