Skip to main content
Glama
Sign In
mcp-brasilapi

mcp-brasilapi

by silasrm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

fipe__listar_tabelas

Retrieve available FIPE reference tables and their corresponding months to identify valid periods for vehicle price queries.

Instructions

Lista as tabelas de referência da FIPE (meses de referência disponíveis).

Returns: Lista de tabelas com codigo e mes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fipe__listar_tabelas"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The description states the tool returns a list with code and month, which is adequate for a simple read operation. However, with no annotations provided, it does not disclose any side effects, authentication needs, or rate limits, but these are not critical for a list tool.

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?

The description is very short (two sentences) and front-loaded with the purpose. It is efficient but could be slightly more structured with explicit headings or bullet points.

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?

Given the tool's simplicity (no parameters, no nested objects) and the presence of an output schema, the description adequately explains the return values (list with code and month), making it complete for its context.

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?

The input schema has no parameters, and the description adds no parameter information. Since schema_description_coverage is 100% (0 params), a baseline of 3 is appropriate.

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 the tool lists FIPE reference tables (available reference months), which is specific and distinguishes from sibling tools like fipe__listar_marcas or fipe__listar_veiculos that list other types of data.

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?

The description implies usage is for obtaining available reference months, but does not explicitly state when to use this tool over alternatives like fipe__listar_marcas or fipe__listar_veiculos, nor any exclusions or prerequisites.

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