Skip to main content
Glama

Fipe API

get_vehicle_by_plate

Read-only

Get the vehicle data and the FIPE prices for a Brazilian license plate. Requires a 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": {
      "plate": "<plate>"
    },
    "name": "get_vehicle_by_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
plateYesBrazilian license plate in the old format (ABC1234) or the Mercosul format (ABC1D23)

Output Schema

NameRequiredDescriptionDefault
cityYes
fuelYes
yearYes
brandYes
colorYes
modelYes
plateYes
powerYes
stateYes
chassisYes
segmentYes
importedYes
fipePricesYes

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 safety and external dependency are covered. The description adds real value by disclosing the subscription-token requirement and that FIPE pricing is bundled into the response, but it leaves idempotentHint=false unexplained; an agent would benefit from knowing whether each call consumes quota or credits.

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 short sentences with the resource and the auth prerequisite front-loaded. Nothing is redundant or padded.

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 single-parameter read tool with an output schema, the description covers purpose, data returned, and the auth prerequisite. Only the practical consequence of non-idempotency (quota consumption, rate limits, invalid-plate errors) is left unaddressed.

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 coverage is 100% and the single plate parameter already documents both accepted formats (ABC1234 and ABC1D23). The description adds no further meaning beyond what the schema provides, which is the expected baseline for a fully documented 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 names a specific verb and resource: retrieving vehicle data plus FIPE prices keyed on a Brazilian license plate. That scope is clear enough to separate it from get_vehicle_by_fipe_code, though the description never explicitly names the alternative lookup key.

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 usage condition is implicit: call it when you have a license plate rather than a FIPE code or model name. The prerequisite of a subscription token is stated, which is genuinely useful, but there is no explicit when-not guidance or named alternative for other lookup inputs.

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