Dados Abertos Senado BR MCP

Detalhar reunião de comissão

senado_reuniao_comissao

Read-onlyIdempotent

Detalha uma reunião de comissão. Aceita DOIS caminhos: o codigoReuniao direto, ou sigla da comissão mais data (YYYYMMDD) — neste segundo caso a ferramenta resolve o código sozinha, e devolve as candidatas quando o dia tem mais de uma reunião. Retorna um objeto com codigo, titulo, comissao, data, hora, local, situacao, realizada, secreta, tipoPresenca (presencial/semipresencial), presidente, links urlPauta/urlResultado/urlAta e partes (cada parte com evento e itens apreciados: identificacao, ementa, autoria, relatoria, resultado, codigoMateria). A API NÃO publica lista de presença da reunião (só presidente e eventuais convidados): reconstrua a presença pelos votos nominais (senado_votacao_comissao), por quem falou na transcrição (senado_notas_taquigraficas com tipo=reuniao) ou pela ata oficial (urlAta, quando publicada). Sem código à mão, prefira sigla + data; o codigoReuniao também sai de senado_agenda_comissoes ou senado_reunioes_comissao.

Input Schema

TableJSON Schema

Name	Required	Description
`data`	No	Data da reunião (YYYYMMDD) — usada com `sigla`; sem ela, os últimos 14 dias
`sigla`	No	Sigla da comissão (ex.: CAE) — alternativa ao código
`codigoReuniao`	No	Código da reunião (campo 'codigo' na agenda). Sem ele, informe sigla e data.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed4 schema fields changedSep 10, 2026

changedInput schema / properties / codigoReuniao / description

Previous value: -"Código da reunião (campo 'codigo' na agenda de comissões)"New value: +"Código da reunião (campo 'codigo' na agenda). Sem ele, informe sigla e data."

addedInput schema / properties / data

Added value: +{
+  "description": "Data da reunião (YYYYMMDD) — usada com `sigla`; sem ela, os últimos 14 dias",
+  "pattern": "^\\d{8}$",
+  "type": "string"
+}

addedInput schema / properties / sigla

Added value: +{
+  "description": "Sigla da comissão (ex.: CAE) — alternativa ao código",
+  "minLength": 2,
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "codigoReuniao"
-]
```

Changed2 schema fields changedAug 31, 2026

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"

Changed3 schema fields changedJun 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / codigoReuniao / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedJun 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedJun 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds substantive behavior: multi-meeting days return candidate lists, and the API does not publish attendance lists, with three concrete reconstruction strategies (votos nominais, notas taquigráficas, urlAta). This is real operational context beyond structured fields.

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?

Front-loaded with purpose, then paths, then return shape, then caveats. The long enumeration of return fields is somewhat redundant given a formal output schema exists, but the overall density is high and little is 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?

Covers lookup paths, resolution behavior, absence of attendance data, and cross-tool workarounds. With the output schema handling return structure and annotations handling safety, nothing an agent needs to invoke 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 adds the interaction logic the schema only hints at: sigla+data triggers automatic code resolution, and the fallback window when data is used alone. It goes beyond field-level definitions.

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+resource ('Detalha uma reunião de comissão'), immediately distinguishing it from list-oriented siblings like senado_reunioes_comissao and senado_agenda_comissoes. An agent can tell this is a single-record detail fetch without opening any 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 describes two accepted lookup paths and states a preference ('Sem código à mão, prefira sigla + data'). It also names where the codigoReuniao comes from (senado_agenda_comissoes, senado_reunioes_comissao), routing the agent between siblings.

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 tools Inspect

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.