Dados Abertos Senado BR MCP

Detalhar matéria legislativa

senado_obter_materia

Read-onlyIdempotent

Obtém dados de uma matéria pelo codigoMateria, conforme secao (padrão detalhe): detalhe → objeto com identificacao, apelido, ementa, autor, situacao, localAtual, dataApresentacao, indexacao, classificacoes[], tramitando, relator (nome/partido/uf/comissão), deliberacao e normaGerada. tramitacao → histórico de tramitação cronológico em tramitacoes[] (data, local, descricao), com count/total (mantém os mais recentes ao truncar). textos → documentos da matéria em textos[] (tipo, formato, identificacao, data, autoria, url), do mais recente ao mais antigo. limite aplica-se a tramitacao/textos (padrão 100 e 50; ao truncar inclui aviso). Obtenha o codigoMateria via senado_buscar_materias.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`secao`	No	detalhe (situação/relator), tramitacao (histórico) ou textos (documentos)	detalhe
`limite`	No	Máximo de itens em tramitacao/textos (padrão: 100 tramitacao, 50 textos)
`codigoMateria`	Yes	Código único da matéria

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 / codigoMateria / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed2 schema fields changedJun 14, 2026

addedInput schema / properties / limite

Added value: +{
+  "description": "Máximo de itens em tramitacao/textos (padrão: 100 tramitacao, 50 textos)",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / secao

Added value: +{
+  "default": "detalhe",
+  "description": "detalhe (situação/relator), tramitacao (histórico) ou textos (documentos)",
+  "enum": [
+    "detalhe",
+    "tramitacao",
+    "textos"
+  ],
+  "type": "string"
+}

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

Behavior5/5

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

Annotations already cover read-only/idempotent/openWorld, yet the description adds substantive behavior: ordering (cronológico, most-recent-first), truncation semantics (`count`/`total`, keeps the most recent, emits an `aviso`) and per-section default limits. These are the operational traits an agent needs and they are not derivable from the annotations.

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 the primary purpose and the source of the ID. Every clause maps to a distinct behavior or return shape, though the wall-of-backticks format is heavy to parse.

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?

Even though an output schema exists, the description fully characterizes each section's payload and the truncation contract, and routes the agent to the search tool for the required ID. Nothing needed to invoke 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 coverage is 100% so the baseline is 3, but the description adds per-section meaning for `secao` (what each mode returns) and the different default `limite` values per mode plus the truncation notice, going meaningfully beyond the schema strings.

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 (obter/detalhar) and resource (matéria legislativa) and immediately distinguishes itself from the search sibling by noting that `codigoMateria` comes from `senado_buscar_materias`. The three `secao` modes are enumerated, so an agent knows exactly what this retrieval tool returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear prerequisite/workflow: obtain `codigoMateria` via `senado_buscar_materias`, then call this to detail it. It explains which `secao` to pick for which need (situação/relator, histórico, documentos). It does not state explicit when-not-to-use cases, so it stops short of a 5.

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.