Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

senado_ecidadania_consultas_analise

Read-onlyIdempotent

Analyzes open e-Cidadania public consultations by consensus (high agreement) or polarization (even split), ordered by concentration or balance of votes.

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
limiteNoNúmero máximo de resultados
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
minimoVotosNoMínimo de votos para considerar
percentualMinimoNoModo consenso: percentual mínimo numa direção
margemPolarizacaoNoModo polarizada: considera polarizado se diferença ≤ este percentual

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true. The description adds significant behavioral context: explains modes, status behavior (including the limitation on encerrada), ordering criteria, default values, and return format. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sentences and front-loaded purpose. It is slightly verbose but each sentence adds value. Could be slightly more concise without losing clarity.

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?

Given the complexity (6 parameters, modes, status nuances, defaults, limitations) and presence of output schema, the description covers all necessary aspects: modes, ordering, status, defaults, limitation, return format, and sibling tool reference. Complete for an analysis tool.

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 description coverage is 100%, so baseline is 3. The description adds semantic detail beyond schema, e.g., explaining how percentualMinimo and margemPolarizacao work in each mode, and the meaning of the return object.

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 description clearly states the tool analyzes public consultations by agreement degree (consenso or polarizada), differentiating from sibling tools like senado_ecidadania_obter_consulta. It specifies the verb 'analisa' and the resource 'consultas públicas abertas (matérias em tramitação)'.

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 explains when to use each mode, the meaning of status options (aberta, encerrada, todas), and mentions the sibling tool for detail. It provides defaults and limitations (e.g., closed consultations before first load not captured), but lacks explicit when-not-to-use guidance.

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