mcp-brasil

Listar marcas na Tabela FIPE

fipe_marcas

Read-onlyIdempotent

Lists Brazilian FIPE vehicle brands by type (cars, motorcycles, trucks), with optional name filtering to find manufacturer brands for pricing and lookup.

Instructions

Lista as marcas de veículos da Tabela FIPE por tipo (carros, motos ou caminhões). Aceita filtro por nome.

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

Input Schema

Name	Required	Description	Default
`tipo`	Yes	Tipo de veículo
`busca`	No	Trecho do nome da marca (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered without description help. The description adds only that a name filter exists, and says nothing about result ordering, completeness of the list, or behavior on an unmatched filter, which is the remaining relevant context.

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, front-loaded with the resource and scope, with the optional filter noted second. No filler or redundant restatement of the tool name.

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?

This is a simple two-parameter read-only lookup with no output schema, and "Lista as marcas" adequately conveys that the result is a set of brand names. Minor gaps remain around result shape/ordering and empty-filter behavior, but nothing essential for correct invocation is missing.

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 the enum for tipo is declared in the schema, so the description's mention of "carros, motos ou caminhões" duplicates structured data. It does not clarify whether "busca" is case-sensitive, accent-insensitive, or a prefix vs. substring match beyond the schema's "Trecho do nome".

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?

"Lista as marcas de veículos da Tabela FIPE" gives a specific verb (list) plus resource (vehicle brands) and constrains the domain to the FIPE table, with the type dimension spelled out. It is clear enough to distinguish from price/lookup siblings like fipe_preco, but it never names an alternative explicitly.

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?

Usage is only implied: the agent can infer it should call this to enumerate brands before querying a specific model or price. There is no statement of when to prefer a sibling (e.g. fipe_preco) or what happens when the filter returns nothing.

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

Deploy Server