Skip to main content
Glama
Sign In
mcp-legislacao-br

mcp-legislacao-br

by wall-e-assessor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

artigo_camara

Retrieves the text of a Chamber of Deputies legislative article from current or original compilations, or via a Legin page URL, to support Brazilian federal legislation research.

Instructions

Texto de um artigo na compilação da Câmara dos Deputados.

Por padrão usa a "Compilação Monovigente na CD" servida pelo normas.leg.br (versao="Current"); versao="Original" traz a publicação original. Alternativamente, informe url_legin de uma página do Legin (camara.leg.br).

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": {
      "artigo": "<artigo>"
    },
    "name": "artigo_camara"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoNo
urnNo
tipoNo
artigoYes
numeroNo
versaoNoCurrent
url_leginNo
forcar_ao_vivoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the default data source and the version semantics, which is real behavioral content. It leaves out the meaning of forcar_ao_vivo (which implies a cache/live-fetch tradeoff) and any note on what happens when the article is not found.

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?

Three short sentences with no wasted wording, and the default source and version are front-loaded ahead of the alternative URL path. The opening line is slightly redundant with the tool name.

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

Completeness2/5

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

For an 8-parameter tool with no annotations and no output schema, the description covers a small fraction of what an agent needs, notably the required artigo format and how urn/ano/tipo/numero combine to identify a norm. The version and URL guidance is good but not enough for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate. It explains only versao (with its two values) and url_legin, leaving the required artigo and the identification parameters ano, urn, tipo, and numero, plus forcar_ao_vivo, entirely unexplained.

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 description uses a specific verb and resource (article text from the Câmara dos Deputados compilation) and names the serving source, normas.leg.br. It implicitly distinguishes itself from artigo_planalto by naming the Câmara sources, but never contrasts the two siblings explicitly.

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 gives a default behavior (Compilação Monovigente via versao="Current") and one alternative path (url_legin for a Legin page), which is useful routing. It says nothing about when to prefer artigo_camara over artigo_planalto or the other siblings, nor about prerequisites or failure cases.

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