Dados Abertos Senado BR MCP

Detalhar consulta pública

senado_ecidadania_obter_consulta

Read-onlyIdempotent

Obtém o detalhe de uma consulta pública específica do e-Cidadania. Retorna um objeto com id, materia, ementa, votosSim/votosNao/totalVotos, percentualSim/percentualNao, status, autor, relator, url. O portal não publica o período da consulta: dataAbertura/dataEncerramento (e comissao/linkMateria) vêm sempre null — a consulta abre quando a matéria entra em tramitação e encerra quando sai, refletido em status. O campo comentarios vem null: a página de consulta não possui recurso de comentários. Obtenha o id antes via senado_ecidadania_listar_consultas ou senado_ecidadania_consultas_analise.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ID da consulta pública

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 / 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?

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing output-level gotchas: dataAbertura/dataEncerramento/comissao/linkMateria are always null because the portal does not publish the period, and `comentarios` is always null because the page lacks a comments feature. It also explains the semantic substitute for the missing dates (status transitions when the matéria enters/leaves tramitação), which prevents an agent from misinterpreting nulls as errors.

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-loads the purpose, then layers return fields, then null-field caveats, then the id-prerequisite tip. The middle sentences are dense but each carries non-obvious information; the field enumeration is slightly list-like, keeping it just short of maximal efficiency.

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?

With one required parameter, full schema coverage, and an output schema present, the description still adds the missing behavioral context an agent needs (which returned fields are permanently null and why, plus how to source the id). Nothing required to call it correctly is left unstated.

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% for the single `id` parameter, so the baseline is 3; the description adds provenance value by specifying that the id must come from senado_ecidadania_listar_consultas or senado_ecidadania_consultas_analise. It does not add format or validation detail beyond the schema, so it stays just above baseline.

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 and resource ('Obtém o detalhe de uma consulta pública específica do e-Cidadania') and scopes it to a single record, which cleanly separates it from the sibling listing tools (senado_ecidadania_listar_consultas, senado_ecidadania_consultas_analise). An agent can tell what this returns 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 sibling tools to call first to obtain the required `id` ('Obtenha o `id` antes via senado_ecidadania_listar_consultas ou senado_ecidadania_consultas_analise'), giving a concrete alternative-and-prerequisite path rather than leaving lookup order to inference.

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.