Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

senado_ecidadania_consultas_analise

Read-only

Analyze Brazilian Senate e-Cidadania public consultations by consensus or polarization, filtering by status, minimum votes, and result limit.

Instructions

Analisa o conjunto completo de consultas públicas abertas (matérias em tramitação) do e-Cidadania por grau de concordância cidadã, conforme modo: consenso → consultas com alta concentração de votos numa direção, ordenadas da maior para a menor concentração; usa percentualMinimo (padrão 85%). polarizada → consultas com votação equilibrada (~50/50), ordenadas da menor para a maior diferença sim/não; usa margemPolarizacao (padrão 15 pontos). Analisa por padrão consultas aberta (opinião pública atual). Quando a matéria sai de tramitação a consulta passa a encerrada, então status: "encerrada"/"todas" cobrem o conjunto que foi encerrado desde a ingestão (cresce com o tempo); fechadas antes da 1ª carga não são capturadas. Todos os modos aceitam minimoVotos (padrão 1000) e limite (padrão 10). Retorna { modo, criterio, count, consultas }. Para o detalhe de uma consulta use senado_ecidadania_obter_consulta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modoNoconsenso (alta concordância) ou polarizada (~50/50)consenso
statusNoRecorte do conjunto (padrão: aberta = opinião atual). encerrada cobre consultas que saíram de tramitação desde a ingestão (cresce com o tempo); fechadas antes da 1ª carga não são capturadas.aberta
percentualMinimoNoModo consenso: percentual mínimo numa direção
margemPolarizacaoNoModo polarizada: considera polarizado se diferença ≤ este percentual
minimoVotosNoMínimo de votos para considerar
limiteNoNúmero máximo de resultados

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Adds significant context beyond annotations: explains sorting order, status limitations, and output structure. No contradictions.

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?

Thorough yet efficient: each sentence adds necessary information, well-organized by mode, status, common params, and output.

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?

Completely covers all aspects of the tool's behavior given its complexity, including edge cases and output format.

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 already has 100% description coverage, but the description adds even more context (e.g., defaults, how values affect sorting/ordering).

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?

Clearly states the tool analyzes open public consultations by 'modo' (consenso/polarizada) with detailed parameters, and distinguishes from sibling 'senado_ecidadania_obter_consulta'.

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

Usage Guidelines5/5

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

Explicitly explains when to use each mode and status, including caveats about coverage of closed consultations, and directs to sibling for details.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SidneyBissoli/senado-br-mcp-cloudflare'

If you have feedback or need assistance with the MCP directory API, please join our Discord server