Skip to main content
Glama

Dados Abertos Senado BR MCP

by io.github.SidneyBissoli
OverviewDiscussionsAdmin

Pesquisar votações

senado_search_votacoes
Read-onlyIdempotent

Busca e lista votações do plenário combinando critérios opcionais. Janela temporal: informe dias (últimos N dias, 1-365) para atividade recente, OU dataInicio/dataFim (YYYYMMDD) para um período arbitrário — para um ano inteiro use dataInicio: "AAAA0101" e dataFim: "AAAA1231". Demais filtros: idProcesso, codigoMateria, sigla/numero/ano da matéria, codigoParlamentar e siglaVotoParlamentar. Retorna { count, votacoes } ordenadas da mais recente para a mais antiga; cada item traz codigoSessao, data, materia, codigoMateria, resultado e placar (totalSim/totalNao/totalAbstencao), sem votos nominais. Use senado_obter_votacao com o codigoSessao para os votos de cada senador.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anoNoAno da matéria
diasNoJanela: votações dos últimos N dias (ignorado se dataInicio/dataFim forem informados)
siglaNoSigla do tipo de matéria
numeroNoNúmero da matéria
dataFimNoData fim (YYYYMMDD)
dataInicioNoData início (YYYYMMDD)
idProcessoNoID do processo legislativo
codigoMateriaNoCódigo da matéria
codigoParlamentarNoCódigo do parlamentar
siglaVotoParlamentarNoTipo de voto do parlamentar

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed12 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / ano / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / ano / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / codigoMateria / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / codigoMateria / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / codigoParlamentar / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / codigoParlamentar / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / idProcesso / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / idProcesso / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / numero / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / numero / minimum
      Added value: +-9007199254740991
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  4. Changed1 schema field changed
    • addedInput schema / properties / dias
      Added value: +{
+  "description": "Janela: votações dos últimos N dias (ignorado se dataInicio/dataFim forem informados)",
+  "maximum": 365,
+  "minimum": 1,
+  "type": "integer"
+}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavior beyond that: result ordering (most recent first), the absence of nominal votes, and the exact returned fields. It stops short of mentioning pagination or result-size limits if any exist.

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?

One dense paragraph, front-loaded with purpose then temporal modes then filters then return shape. Every sentence carries information, though the run-on structure with many inline backticked field names is slightly heavy for a single block.

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?

For a 10-parameter, all-optional filter tool with a full output schema and rich annotations, the description covers purpose, argument precedence, return fields, and the drill-down path. Nothing an agent needs to select and call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: the precedence rule that `dias` is ignored when dataInicio/dataFim are supplied (schema only says it in the `dias` doc), the YYYYMMDD format intent, and a grouping of the remaining filters by entity (matéria, parlamentar, voto).

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?

States a specific verb ('Busca e lista') and resource ('votações do plenário') plus the combination-of-optional-criteria behavior, which separates it from senado_votacao_comissao and senado_votacoes_senador. It also names the sibling senado_obter_votacao for drill-down, so an agent can route without opening a schema.

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 frames the two mutually exclusive temporal modes ('informe `dias` ... OU `dataInicio`/`dataFim`'), gives a concrete year-wide example, and states when to switch to senado_obter_votacao for nominal votes. Both the when and the alternative are spelled out.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources