Skip to main content
Glama
Sign In
mcp-brasil

mcp-brasil

by Arthurpereiraa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Preço na Tabela FIPE

fipe_preco
Read-onlyIdempotent

Retrieve average Brazilian FIPE vehicle prices by FIPE code across all available model years, with optional year filtering for used-car valuation.

Instructions

Consulta o preço médio de um veículo na Tabela FIPE pelo código FIPE (ex.: 001004-9), em todos os anos-modelo disponíveis.

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": {
      "codigo_fipe": "<codigo_fipe>"
    },
    "name": "fipe_preco"
  }
}

Input Schema

NameRequiredDescriptionDefault
ano_modeloNoFiltra por ano-modelo (opcional)
codigo_fipeYesCódigo FIPE no formato 000000-0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the safety profile is covered. The description adds one genuine behavioral detail — that omitting ano_modelo returns all available model years — but says nothing about the response shape (list vs. single value), currency/units, or behavior for an invalid code against an open-world external table.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence that front-loads the verb and resource, then the required key and scope — nothing padded. The parenthetical code example is mildly redundant with the schema's own format description, keeping it just shy of a 5.

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?

For a two-parameter lookup with full schema coverage and rich annotations, the description covers what it does, what it needs, and what it broadly returns. The remaining gap is minor: with no output schema, the description could say whether the result is a single average price or a per-year list.

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 both parameters are already documented, and the example "001004-9" only restates the schema's stated format "000000-0". The only added meaning is the implicit default behavior of ano_modelo (all years when absent), which is modest at baseline 3.

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?

States a specific verb and resource ("Consulta o preço médio de um veículo na Tabela FIPE") plus the required input (código FIPE) and the scope (todos os anos-modelo). An agent can distinguish it from unrelated siblings like consultar_cnpj or calcular_dias_uteis, though it never names fipe_marcas as the source of the code.

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 implied by the resource: look up a FIPE price when you already have a FIPE code. There is no explicit when-not guidance, no note on how to obtain a código FIPE, and no pointer to a sibling for brand/model lookup or for the annual-model variants of the same table.

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

Deploy Server

Other Tools