Skip to main content
Glama
rtc-calculadora-mcp

rtc-calculadora-mcp

by tmoreiradev

consultar_aliquota_referencia

Look up official reference CBS/IBS tax rates by sphere, date, and IBGE code (UF or municipality) for Brazil’s consumption-tax reform; returns 2026 rates or nominal rates after 2027.

Instructions

Aliquota de referencia oficial (%): uniao = CBS, uf = IBS estadual, municipio = IBS municipal. codigo_ibge e o codigo da UF (ex.: 43) ou do municipio (ex.: 4314902). A tabela oficial so tem aliquotas para 2026; a partir de 2027 a consulta falha e as aliquotas vao em aliquotasNominais.

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": {
      "esfera": "<esfera>",
      "data": "<data>"
    },
    "name": "consultar_aliquota_referencia"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
esferaYes
codigo_ibgeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and usefully discloses that official rates exist only for 2026 and that queries fail from 2027, with values moving to aliquotasNominais. It does not state conditional codigo_ibge requirements or other error behavior.

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?

Three tightly packed sentences, front-loaded with the resource and sphere mapping. Backticked field names aid scanning and there is no redundant wording.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. The description covers purpose, sphere mapping, IBGE code format, and the 2026/2027 failure mode, but omits whether codigo_ibge is required for uf/municipio and exact data semantics, which are important for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must add meaning. It explains the esfera enum mapping and describes codigo_ibge as a UF or municipality IBGE code with examples; data is only indirectly covered by the 2026 restriction, and the conditional need for codigo_ibge is not explicit.

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 the resource as the official reference rate and maps each esfera to CBS or IBS, so an agent can recognize it as a rate lookup. It lacks an explicit verb and does not contrast with calcular_tributos, but the resource is distinct enough.

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?

No explicit when-to-use or alternative routing is given; usage is only implied by the official-rate purpose. The 2026-only table and 2027 failure note act as a usage constraint, but not as sibling guidance.

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