Skip to main content
Glama

Dados Abertos Senado BR MCP

by io.github.SidneyBissoli

Tabelas de referência

senado_tabelas_referencia
Read-onlyIdempotent

Consulta tabelas de referência do Senado pelo parâmetro tabela. Valores: tipos-materia → { count, tipos } (sigla/nome/descricao dos tipos de proposição, p.ex. PEC, PL, MPV) — catálogo curado mantido neste servidor (12 tipos mais comuns, não é a lista viva do upstream processo/siglas, que tem ~184 siglas); use para achar a sigla correta antes de senado_buscar_materias/senado_search_processos; partidos → { count, totalSenadores, partidos } (partidos com bancada atual, ordenados por nº de senadores); ufs → { count, totalSenadores, ufs } (as 27 UFs com a contagem de senadores em exercício); legislatura-atual → { numero, periodo, dataInicio, dataFim } da legislatura vigente; tipos-norma → { count, tipos } (sigla/descricao dos tipos de norma para senado_buscar_legislacao); tipos-uso-palavra → { count, tipos } (codigo/descricao para interpretar tipoUsoPalavra em senado_discursos_senador). Toda resposta inclui o campo tabela. Para a relação nominal de parlamentares use senado_listar_senadores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabelaYesQual tabela de referência consultar: tipos-materia, partidos, ufs, legislatura-atual, tipos-norma ou tipos-uso-palavra

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds meaningful behavioral context: it is a curated cache ('catálogo curado mantido neste servidor') with only 12 common tipos versus the upstream ~184 siglas, notes that every response includes the `tabela` field, and discloses ordering for partidos.

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?

Although the description is long, every segment is load-bearing: each of the six options receives one compact line combining output shape, semantics, and usage. It is front-loaded with the core definition and uses bolded enum keys and em-dashes for scannability. No wasted sentences.

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?

Covers every enum value, all output shapes, relevant sibling routing, and a critical caveat about the curated nature of the data. With an output schema present and a single required parameter, nothing an agent needs to select and invoke the tool 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 coverage is 100%, so baseline is 3, but the description substantially enriches the lone `tabela` parameter by explaining each enum value's output shape, purpose, and downstream consumer tool. This goes well beyond the schema's single-line enum description.

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?

Specific verb 'Consulta' + resource 'tabelas de referência do Senado' via parameter `tabela`, with all six enum values enumerated and their return shapes spelled out. It distinguishes itself from search tools by naming them (senado_buscar_materias, senado_search_processos, senado_buscar_legislacao, senado_discursos_senador).

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 tells when to use which value: 'use para achar a sigla correta antes de senado_buscar_materias/senado_search_processos', maps tipos-norma to senado_buscar_legislacao, and tipos-uso-palavra to interpreting senado_discursos_senador. It also routes nominal parliamentary lists to senado_listar_senadores.

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