Série temporal de preços de um veículo ao longo dos meses de referência (a CURVA DE DEPRECIAÇÃO — o diferencial vs. consultar o site). Retorna [{ referencia, mes, valor }] do mais antigo ao mais recente.
| Name | Required | Description | Default |
|---|---|---|---|
| ano_modelo | Yes | ||
| codigo_fipe | Yes | ||
| combustivel | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds value by specifying the return format (list of objects with referencia, mes, valor) and ordering (oldest to newest). There is no contradiction with 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?
The description consists of two concise sentences. The first defines the tool's purpose and value proposition, and the second specifies the return format and ordering. No unnecessary information is included.
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?
Given the complexity (3 parameters, no output schema), the description is incomplete: it does not explain input parameters or clarify how to use them. It also does not differentiate usage from sibling tools like 'fipe_preco' or 'fipe_buscar'.
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?
The schema has 0% description coverage, and the tool description does not explain any of the three parameters (codigo_fipe, ano_modelo, combustivel). This is a significant gap as the description fails to add meaning beyond parameter names.
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?
The description clearly states the tool returns a time series of vehicle prices over reference months, specifically calling it a 'depreciation curve' and distinguishing it from consulting the website. It uses a specific verb ('retorna') and defines the resource (historical prices).
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?
The description implies use for historical price data versus current price tools like 'fipe_preco', but does not explicitly state when to use this tool over siblings. No exclusions or alternative recommendations are provided.
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.