Lista os anos-modelo (com combustível) disponíveis para um modelo. Retorna [{ ano_modelo, combustivel }] (ex.: '2020-1' = 2020 gasolina). Use a tupla resultante em fipe_preco.
| Name | Required | Description | Default |
|---|---|---|---|
| codigo_marca | Yes | ||
| tipo_veiculo | Yes | ||
| codigo_modelo | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly and idempotent. Description adds return format and example, enhancing transparency beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with action and output format. No redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Partially explains output and links to next tool, but lacks parameter details and overall flow context given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet description gives no parameter descriptions. Parameter names are somewhat self-explanatory, but the description fails to compensate for the lack of schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it lists model-years with fuel for a model, with an example and direction to fipe_preco. It distinguishes from sibling FIPE tools but does not explicitly connect to the required parameters.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Specifies to use the result in fipe_preco, providing clear context. No exclusions or when-not-to-use guidance, but sufficient for a sequential workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.