mcp-brasilapi

by silasrm

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

fipe__listar_veiculos

Retrieve a list of vehicles for a specified brand and vehicle type (car, motorcycle, or truck) using FIPE table data.

Instructions

Lista os veículos de uma marca conforme o tipo.

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": {
      "tipo_veiculo": "<tipo_veiculo>",
      "codigo_marca": "<codigo_marca>"
    },
    "name": "fipe__listar_veiculos"
  }
}

Input Schema

Name	Required	Description	Default
`codigo_marca`	Yes	Código da marca retornado por ``fipe__listar_marcas``.
`tipo_veiculo`	Yes	``carro``, ``moto`` ou ``caminhao``.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the basic functionality without mentioning read-only behavior, error handling, pagination, or any constraints beyond the input validation already in the schema.

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?

The description is a single efficient sentence with no superfluous words, front-loading the key action and resource.

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?

Given that an output schema exists (though not shown), the description provides enough context for a simple list operation. However, it could slightly benefit from mentioning that it returns a list of vehicle models or codes, but the output schema fills that gap.

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%, so baseline 3. The description adds no additional parameter information beyond what is already in the schema. The parameter descriptions in the schema are sufficient.

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 'Lista os veículos de uma marca conforme o tipo' clearly states the action (list vehicles), the resource (by brand and type), and differentiates from sibling tools like listar_marcas (which lists brands) and consultar_preco (which gets prices).

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 description implies usage after obtaining the brand code from fipe__listar_marcas, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.