fipe_modelos
Read-onlyIdempotent
Lista os modelos de uma marca. Retorna [{ codigo_modelo, modelo }]. Use o codigo_marca obtido em fipe_marcas.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| codigo_marca | Yes | ||
| tipo_veiculo | Yes |
Tabela FIPE
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 destructiveHint. The description adds the return format but no additional behavioral context beyond what annotations imply, earning a baseline score.
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 extremely concise with no superfluous words, front-loading the key action and output format in two sentences.
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?
While the tool is simple and annotations cover safety, the description omits parameter semantics and lacks an output schema. The return structure is mentioned but insufficient for a complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has zero description coverage, and the description does not explain the purpose or possible values of the two parameters, especially tipo_veiculo, leaving the agent without critical information.
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 clearly states that the tool lists models for a brand, specifies the return structure, and references the prerequisite tool fipe_marcas, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides explicit guidance to use the codigo_marca from fipe_marcas, establishing a clear dependency. However, it does not explain when not to use this tool or suggest alternatives for similar functionality.
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.
TDQS
A3.9/5.0
Disambiguation4/5
The seven fipe_* tools each target a distinct step in the FIPE data lookup (brands, models, years, price, history, search, reference dates), and their names make their purposes clear. However, connect and toolkit_info both report connection status, and marketplace bundles many sub-operations into one tool, creating minor ambiguity.
Naming Consistency3/5
FIPE tools follow a consistent fipe_<noun> pattern, but the platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) use generic verbs/nouns without a shared convention, mixing styles within the same server.
Tool Count5/5
13 tools is within the ideal range for a domain-specific data server; the 7 FIPE tools are well-scoped and the 6 platform utilities are justified for authentication, marketplace access, and system status.
Completeness5/5
The FIPE data surface is complete: marcas → modelos → anos → preco covers the full drill-down, with buscar, historico, and tabelas_referencia adding search, time series, and date selection. No obvious missing operations for the domain.