mcp-brasilapi

by silasrm

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

ncm__buscar

Retrieve detailed information about a Brazilian NCM code by entering the exact code, with or without periods.

Instructions

Busca um NCM a partir do código exato.

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": {
      "code": "<code>"
    },
    "name": "ncm__buscar"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	Código NCM, com ou sem pontos (ex.: "3305.10.00" ou "33051000").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the action but does not disclose any behavioral traits (e.g., read-only, rate limits, error handling). However, given the simplicity of a lookup tool, the lack of deeper disclosure is acceptable but not exemplary.

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 a single, concise sentence that delivers the essential information immediately. There is no redundancy or unnecessary text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, output schema exists), the description sufficiently covers the tool's purpose. The output schema handles return value documentation, so no additional description is needed.

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 covers 100% of the parameters with a detailed description of 'code' (format examples). The description adds 'código exato' which reinforces exactness, but this is already implied by the schema description. Thus, no significant additional meaning is provided beyond the schema.

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 verb 'Busca' (searches) and the resource 'NCM' with the specific scope 'a partir do código exato' (from exact code). It differentiates from sibling tools like ncm__listar and ncm__pesquisar, which imply listing or broader search.

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 for exact code lookups but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. The sibling names (listar, pesquisar) offer implicit guidance, but direct instructions are missing.

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