Dados Abertos Senado BR MCP

Histórico do senador

senado_senador_historico

Read-onlyIdempotent

Histórico funcional de um senador conforme o parâmetro tipo. Valores: licencas (itens com dataInicio/dataFim/descricao), comissoes (sigla/nome/casa/participacao/datas), cargos (comissao/cargo/datas), historico-academico (cursos, registros brutos da API), filiacoes (partido/nomePartido/dataFiliacao/dataDesfiliacao) e profissoes (nome). Retorna { codigoSenador, tipo, count, itens }, com a forma de cada item dependente do tipo; tipos sem registros para o senador retornam count 0 e itens vazio. Requer codigoSenador (obtenha via senado_listar_senadores). Para dados biográficos e mandatos use senado_obter_senador. Ex.: { codigoSenador: 4994, tipo: 'filiacoes' } → histórico de partidos do senador.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tipo`	Yes	Qual histórico consultar
`codigoSenador`	Yes	Código único do senador

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 changedJun 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / codigoSenador / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedJun 14, 2026

changedInput schema / properties / tipo / enum

Previous value: -[
-  "licencas",
-  "comissoes",
-  "cargos",
-  "historico-academico"
-]New value: +[
+  "licencas",
+  "comissoes",
+  "cargos",
+  "historico-academico",
+  "filiacoes",
+  "profissoes"
+]

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.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), but the description goes further by disclosing the empty-result edge case (count 0, empty itens) and that item shape varies by `tipo`. It stops short of auth/rate-limit or pagination context, so it is strong but not exhaustive.

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 the purpose, then the enum semantics, then return shape, then the sibling pointer, then an example — a logical progression. Some of the per-`tipo` field listing overlaps with the output schema, which is mild redundancy in an otherwise dense single paragraph.

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?

An output schema exists, so return values need not be restated, yet the description supplies the edge case (no records) and the shape-shifting item semantics that the schema alone would not convey. Together with the sibling routing and prerequisite, an agent has everything needed to call it correctly.

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 baseline is 3, but the description adds real meaning beyond the schema's terse 'Qual histórico consultar' by mapping each enum value to the fields it returns (e.g. `filiacoes` → partido/nomePartido/datas) and giving a worked example. That is genuine semantic value over the enum list.

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 combination (functional history of a senator, parameterized by `tipo`) and enumerates exactly which histories are covered. It also distinguishes itself from the sibling `senado_obter_senador`, so the agent can route correctly without opening the 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 names the alternative and its condition: biographical data and mandates go to `senado_obter_senador`, while this tool serves functional history. It also tells the agent how to source `codigoSenador` (via `senado_listar_senadores`). No inference required.

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.