Skip to main content
Glama

consultar_fundamentacao_legal

Retrieves the legal basis under LC 214/2025 for a tax classification (cClassTrib) or searches legal texts by keyword, helping verify supporting legislation for CBS/IBS/IS calculations.

Instructions

Consulta a fundamentação legal (LC 214/2025) de cada cClassTrib.

Informe c_class_trib para a base legal de uma classificação, ou busca para filtrar por texto.

Args: data: Data (yyyy-MM-dd). Padrão: hoje. c_class_trib: Código da cClassTrib. busca: Texto livre (ex: 'medicamento', 'art. 138'). limite: Máximo de itens (padrão 10; os textos legais são longos).

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": "consultar_fundamentacao_legal"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
buscaNo
limiteNo
c_class_tribNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole behavioral burden. "Consulta" marks it as a read operation, and the note that the legal texts are long explains why a `limite` exists. It does not say what a record contains or what happens if no argument is passed, even though no parameter is required.

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 purpose comes first in a single sentence, and the argument list is packed into four short lines with no filler. Nothing is repeated from the schema by accident, because the schema carries no descriptions to repeat.

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?

There is no output schema, and the description never says what comes back, for example a list of legal citations per cClassTrib. It also does not say what happens with no arguments, even though all four parameters are optional. The modes it does describe are clear, so it is adequate rather than complete.

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?

With 0% schema coverage, the description has to document all four parameters, and it does: `data` defaults to today, `c_class_trib` selects a classification, `busca` takes free text with examples like 'medicamento' and 'art. 138', and `limite` defaults to 10. It does not explain why legal grounding depends on a date, which leaves the most unusual parameter only half defined.

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?

The first sentence gives a concrete verb plus resource: it reads the legal basis (LC 214/2025) attached to a cClassTrib. That is specific enough that an agent can tell it apart from sibling tools such as consultar_nbs or buscar_classificacao_tributaria. It stops short of 5 because it never names an alternative tool.

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?

It says to pass `c_class_trib` for the legal basis of a single classification, or `busca` to filter by text, so the caller can pick a mode. It gives no when-to-use versus alternatives and no when-not-to-use. The two modes are implied rather than stated as a rule.

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