Skip to main content
Glama

Fipe API

list_brands

Read-only

List the vehicle brands for a vehicle type.

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

Input Schema

NameRequiredDescriptionDefault
referenceNoreference code from list_references; omit it for the latest month
vehicle_typeYesvehicle type: cars, motorcycles or trucks

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=false, so the safety and openness profile is covered. The description adds nothing beyond that — it doesn't mention that omitting `reference` yields the latest month, whether an invalid vehicle_type errors or returns empty, or whether the upstream data is external and volatile (relevant given openWorldHint).

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 or redundancy. It is efficient, though the brevity is closer to under-specification than to disciplined compression given the tool's filtering and reference-month behavior.

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 needn't be explained, and the input schema fully documents both parameters. Still, for an open-world, non-idempotent lookup the description leaves open how the vehicle_type filter behaves, whether results are paginated or exhaustive, and what the reference month means in practice — gaps the schema alone doesn't close.

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%, including the enumeration-ish hint for vehicle_type and the note that reference omitting yields the latest month, so the schema already carries parameter meaning. The description only restates the vehicle_type constraint and says nothing about `reference`, so it neither adds nor subtracts meaning. Baseline 3 applies.

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 ("List the vehicle brands") plus the scoping dimension ("for a vehicle type"), which is enough to distinguish it from siblings like list_models or list_references. It stops short of explicitly naming how it differs from those siblings, so it's clear but not maximally differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative. The statement that results are keyed to a vehicle type only implies the tool's role; an agent must infer that it should call this before list_models and must supply a vehicle_type obtained elsewhere.

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