Skip to main content
Glama

Dados Abertos Senado BR MCP

by io.github.SidneyBissoli

Resultados do plenário

senado_resultado_plenario
Read-onlyIdempotent

Resultado das sessões plenárias numa data: itens de pauta apreciados, pareceres e resultados. Retorna { data, escopo, count, sessoes } (todas as sessões da data, sem paginação), com cada sessão trazendo codigoSessao, numeroSessao, data, hora, tipo, casa e itens (codigoMateria, identificacao, ementa, resultado, parecer — resultado/parecer podem vir null em itens ainda não deliberados). Sem sessão na data, count é 0 e sessoes vem vazio. escopo: sf (Senado), cn (Congresso) ou mes (resumo do mês). Para a pauta prévia use senado_agenda_plenario; orientação de bancada via senado_orientacao_bancada.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesData da sessão (YYYYMMDD); para escopo=mes, qualquer dia do mês
escopoNosf = Senado no dia; cn = Congresso no dia; mes = resumo do mêssf

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the bar is lower. The description adds valuable behavioral detail beyond the annotations: all sessions are returned without pagination, resultado/parecer may be null for undeliberated items, and count is 0 with empty sessoes when no session exists. No contradiction with annotations.

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 compact and well-structured: core purpose first, then return shape, edge-case behavior, escopo meanings, and sibling-tool routing. Every phrase earns its place and there is no redundant filler.

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 that an output schema exists, the description covers the remaining practical context: return shape, no pagination, nullable fields, empty-response behavior, scope semantics, and alternatives. An agent has everything needed to select and invoke this tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already explains the YYYYMMDD pattern and the escopo enum/default. The description reinforces these meanings but does not add substantial new parameter semantics beyond what the schema provides, so the baseline of 3 applies.

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 opens with a specific verb and resource: it returns plenary session results for a date, including agenda items, opinions, and outcomes. It also explicitly names sibling tools it is not (senado_agenda_plenario, senado_orientacao_bancada), so an agent can disambiguate it without opening schemas.

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?

It states the use case (plenary results for a date), explains the escopo variants, and gives explicit routing: use senado_agenda_plenario for the prior agenda and senado_orientacao_bancada for bench orientation. This is clear when-to-use and 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.

All Dados Abertos Senado BR MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation2/5

Several tools perform overlapping functions (e.g., senado_buscar_materias vs senado_search_processos, senado_contratos vs senado_contratacoes_lista, and three e-cidadania consultation tools). Although descriptions are detailed, an agent can easily select the wrong one without deep inspection.

Naming Consistency3/5

All tools share the 'senado_' prefix, but the pattern is inconsistent: some use Portuguese verbs (buscar, listar, obter), others English 'search', and some are bare nouns (senado_ceaps, senado_mesa, senado_vetos). This mixed convention reduces predictability.

Tool Count2/5

67 tools is far above the 25 threshold, indicating an overgrown surface. While each tool may serve a niche endpoint, the sheer number makes it difficult for an agent to choose efficiently, and many tools could be consolidated.

Completeness4/5

The toolset covers nearly every aspect of Senate open data (legislative, senatorial, committee, administrative, financial, e-cidadania) with list/detail/searches. Minor gaps exist, such as no direct consolidated contract search, but most workflows can be achieved.

Resources