Skip to main content
Glama

Fipe API

list_models

Read-only

List the models of a brand.

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

Input Schema

NameRequiredDescriptionDefault
referenceNoreference code from list_references; omit it for the latest month
brand_codeYesbrand code from list_brands, for example 59
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 profile is covered structurally. The description adds nothing beyond annotations — no statement about coverage, pagination, or what happens when reference is omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no wasted words, but it is under-specified rather than well-sized — the terse phrasing leaves real gaps instead of earning its place through precision.

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?

The tool is simple, the schema is fully documented, an output schema exists, and annotations cover safety, so the bar is low. Still, the description omits how this relates to list_model_years and what the reference parameter changes, leaving contextual gaps.

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 the parameters (reference, brand_code, vehicle_type) are fully documented in the schema, including the note that reference comes from list_references. Baseline 3 applies since the description contributes no additional parameter meaning.

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 gives a specific verb and resource ("List the models") scoped to a brand, which is enough for an agent to know what comes back at a high level. It does not distinguish this from siblings such as list_model_years, so it stops short of 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 Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. The only routing hints come from the input schema's mentions of list_brands and list_references, not from the description itself.

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