mcp-camara-pecs

listar_pecs

Find Brazilian constitutional amendment proposals (PECs) using filters like year, keywords, or date range, and retrieve their IDs for use in related tools.

Instructions

Lista Propostas de Emenda à Constituição (PECs).

Use para descobrir PECs e obter o `id` de cada uma (necessário nas demais
ferramentas). Filtros são opcionais e combináveis.

Parâmetros:
- ano: ano de apresentação (ex.: 2023).
- numero: número da proposição.
- keywords: termos de busca na ementa/palavras-chave (ex.: "reforma tributária").
- data_apresentacao_inicio / data_apresentacao_fim: intervalo AAAA-MM-DD.
- ordenar_por: campo de ordenação ("id", "ano", "numero").
- ordem: "ASC" ou "DESC".
- max_itens: teto de resultados retornados (paginação automática).

Input Schema

TableJSON Schema

Name	Required	Default
`ano`	No
`ordem`	No	DESC
`numero`	No
`keywords`	No
`max_itens`	No
`ordenar_por`	No	id
`data_apresentacao_fim`	No
`data_apresentacao_inicio`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It conveys a read-only listing operation through 'Lista' and 'descobrir', discloses that filters are optional and combinable, and mentions automatic pagination with max_itens as a cap. It does not detail API limits, auth, or response format, but the output schema covers the latter.

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 front-loaded with purpose, followed by usage, then a compact parameter list. Every sentence adds value and no information is repeated from the schema.

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?

For a list tool with 8 optional parameters and an output schema, the description covers purpose, usage, all parameter semantics, and key behavioral details. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates by documenting all 8 parameters with concrete examples (ano: 2023, keywords: 'reforma tributária'), value domains for ordenar_por and ordem, date format AAAA-MM-DD, and the meaning of max_itens as a result cap with automatic pagination.

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 first sentence 'Lista Propostas de Emenda à Constituição (PECs)' states a specific verb and resource, and the second clarifies its role as the discovery/ID-gathering entry point ('Use para descobrir PECs e obter o id de cada uma (necessário nas demais ferramentas)'). This clearly separates it from the detail and sub-resource sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent to use this tool when it needs to discover PECs and obtain their ids for downstream tools, and notes filters are optional and combinable. It does not explicitly name alternatives or provide when-not-to-use exclusions, so it falls short of a 5.

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

Deploy Server