Dados Abertos Senado BR MCP

Ranking de autoria/relatoria por comissão

senado_distribuicao_materias

Read-onlyIdempotent

Ranqueia parlamentares pela quantidade de matérias numa comissão (siglaComissao), medindo carga de trabalho legislativo. tipo escolhe o eixo: autoria (matérias de autoria; padrão) ou relatoria (matérias relatadas). Retorna { siglaComissao, tipo, count, parlamentares } ordenado por quantidade desc, sem paginação (count 0 quando a comissão não tem registros), cada item com codigo, nome, partido, uf e quantidade. codigoParlamentar restringe a um parlamentar e só tem efeito em tipo=autoria (ignorado em relatoria). Descubra a sigla via senado_listar_comissoes; use o codigo do parlamentar em senado_obter_senador. Para a lista das matérias em si (não a contagem) use senado_buscar_materias.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tipo`	No	autoria = matérias de autoria por parlamentar (padrão); relatoria = matérias relatadas	autoria
`siglaComissao`	Yes	Sigla da comissão (ex: CCJ, CAE)
`codigoParlamentar`	No	Restringe a um parlamentar — efetivo apenas em tipo=autoria (ignorado em relatoria)

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"

Changed1 schema field changedJul 8, 2026

changedInput schema / properties / codigoParlamentar / description

Previous value: -"Filtrar por parlamentar (apenas tipo=autoria)"New value: +"Restringe a um parlamentar — efetivo apenas em tipo=autoria (ignorado em relatoria)"

Changed4 schema fields changedJun 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / codigoParlamentar / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / codigoParlamentar / minimum
```
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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real behavioral context beyond that: no pagination, output ordered by quantidade descending, and count of 0 when the committee has no records. It also flags the non-obvious silent-ignore behavior of codigoParlamentar under relatoria.

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?

A single dense but well-ordered paragraph: purpose first, then parameter semantics, then return shape, then discovery and alternative routing. Every sentence carries information, though the return-shape enumeration is somewhat heavy given 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?

Given three parameters, an output schema, and full schema coverage, the description supplies everything an agent needs: purpose, the tipo/codigoParlamentar interaction, the empty-result case, and the sibling tools for discovery and for the alternate list-based task.

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 goes further by explaining that tipo selects which workload axis is measured and by explicitly warning that codigoParlamentar is ignored in relatoria — a semantic caveat that prevents a plausible misinvocation.

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 ('Ranqueia parlamentares pela quantidade de matérias numa comissão') and immediately scopes it by the tipo axis (autoria vs relatoria), so an agent can distinguish it from list-oriented siblings. It explicitly names senado_buscar_materias as the tool for the underlying list rather than the count.

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 routes the agent: discover the sigla via senado_listar_comissoes, get the parlamentar codigo from senado_obter_senador, and use senado_buscar_materias when the raw list of matérias is wanted instead of a ranking. It also states the condition under which codigoParlamentar is useful (tipo=autoria) and when it is not (relatoria).

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.