Dados Abertos Senado BR MCP

Vídeos da taquigrafia

senado_videos_taquigrafia

Read-onlyIdempotent

Lista os vídeos e áudios (unidades descritivas) de uma sessão plenária ou reunião de comissão. Retorna { id, tipo, count, total, aviso?, videos } (sessão sem mídia no acervo → count/total 0 com aviso; ao passar de limite inclui aviso). A cobertura de mídia é mais ampla que a das notas: sessões conjuntas do Congresso costumam ter vídeos mesmo sem transcrição, cada item com codigo, data, descricao, orador, duracaoSegundos e os links urlVideo, urlAudio, urlThumbnail. Obtenha o id via senado_agenda_plenario/senado_resultado_plenario (sessão) ou senado_reuniao_comissao (reunião). Para a transcrição textual correspondente use senado_notas_taquigraficas, não esta.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Código da sessão plenária ou da reunião de comissão, conforme `tipo`
`tipo`	No	sessao = plenário (padrão); reuniao = comissão	sessao
`limite`	No	Máximo de unidades (padrão 50, máx 200); o excedente é sinalizado em aviso
`orador`	No	Retorna só unidades cujo orador contém este nome (busca parcial)

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
```

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 changedJul 8, 2026

changedInput schema / properties / id / description

Previous value: -"Código da sessão plenária ou da reunião de comissão"New value: +"Código da sessão plenária ou da reunião de comissão, conforme `tipo`"

changedInput schema / properties / limite / description

Previous value: -"Máximo de unidades (padrão: 50)"New value: +"Máximo de unidades (padrão 50, máx 200); o excedente é sinalizado em aviso"

changedInput schema / properties / orador / description

Previous value: -"Filtra unidades por nome do orador"New value: +"Retorna só unidades cujo orador contém este nome (busca parcial)"

Changed1 schema field changedJul 7, 2026

addedInput schema / properties / limite

Added value: +{
+  "default": 50,
+  "description": "Máximo de unidades (padrão: 50)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

Changed3 schema fields changedJun 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / id / 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 confirm it is a read-only, idempotent, open-world operation, and the description adds substantial extra behavior: the return shape, that sessions without archived media yield count/total 0 plus an `aviso`, that exceeding `limite` emits an `aviso`, and that media coverage is broader than transcripts (joint Congress sessions often have video without transcription). This is real behavioral context beyond the 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 return shape, edge cases, id sourcing, and the alternative. Dense but every sentence carries information; the only mild redundancy is enumerating return fields (`codigo`, `data`, `descricao`, etc.) when an output schema already exists.

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 4-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed: purpose, edge cases (empty media, truncation), id provenance, and the sibling to use for transcripts. Nothing an agent needs to call it 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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains the `limite` overflow signal (`aviso`) and ties the `id` semantics to session vs. committee meeting, clarifying the `tipo` dimension. Minor value-add above the already-complete schema.

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?

Starts with a specific verb and resource ('Lista os vídeos e áudios (unidades descritivas) de uma sessão plenária ou reunião de comissão'), and explicitly distinguishes itself from the sibling senado_notas_taquigraficas ('Para a transcrição textual correspondente use senado_notas_taquigraficas, não esta'). An agent can tell it apart from both the notes tool and the session-listing tools 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?

Names the exact tools that supply the required `id` (`senado_agenda_plenario`/`senado_resultado_plenario` for sessions, `senado_reuniao_comissao` for committee meetings) and names the alternative to use for text transcripts with an explicit exclusion. When-to-use, prerequisite sourcing, and the when-not are all covered.

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.