Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

senado_ecidadania_consultas_votos

Read-onlyIdempotent

Retrieve archived voting results from Brazilian Senate e-Cidadania public consultations, with filters by state, bill, and ranking by vote counts.

Instructions

Acervo histórico de votos das consultas públicas do e-Cidadania, com quebra por UF (fonte: CSV Arquimedes; ~15 mil matérias, atualizado semanalmente). Diferente de senado_ecidadania_listar_consultas (consultas em tramitação): aqui o conjunto é o arquivo de matérias já consultadas — status vem como Descontinuado no arquivo de origem, por isso é tratado como acervo, não como opinião atual. Retorna { count, referencePeriod, consultas }, cada item com id, materia, ementa, autoria, votosSim/votosNao/totalVotos, votosPorUf ({ UF: { sim, nao } }) e url. Use ordenarPor (total/sim/nao, padrão total) e ordem para ranking; uf para recortar e ranquear por aquele estado (só matérias com votos na UF, e cada item ganha recorteUf); materia para filtrar por código (numérico) ou trecho do nome/ementa; limite (padrão 20).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ufNoSigla da UF (ex.: SP) — filtra e ranqueia por votos daquele estado
ordemNoOrdem (padrão desc)desc
limiteNoNúmero máximo de resultados
materiaNoFiltro por código da matéria (numérico) ou trecho do nome/ementa
ordenarPorNoMétrica do ranking (padrão: total de votos)total

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds that data is updated weekly, treats status as historical, and returns specific structure (count, referencePeriod, consultas). 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?

Description is well-structured with bold keywords, uses bullet-like paragraphs, and is concise given the complexity. Could be slightly shorter but still efficient.

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 tool's complexity (5 params, output schema present), the description fully covers purpose, usage, parameters, return structure, and behavioral traits. Output schema exists, so return value details are not needed in description.

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?

All 5 parameters have descriptions in the input schema (100% coverage). The description adds explanatory context about 'ranquear por aquele estado' for 'uf', 'ranking' for 'ordenarPor'/'ordem', and clarifies 'materia' filter semantics.

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 defines the tool as an archive of historical votes with breakdown by UF, and explicitly distinguishes it from the sibling 'senado_ecidadania_listar_consultas' which deals with current consultations.

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?

Provides explicit guidance on when to use this tool (historical archive) vs. the sibling, explains the meaning of the 'status' field, and elaborates on parameter usage like 'uf' for filtering and ranking.

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