Dados Abertos Senado BR MCP

Autores em exercício

senado_autores_atuais

Read-onlyIdempotent

Lista parlamentares autores de processos em tramitação, ordenados por produção (maior número de matérias primeiro). Atenção à semântica: 'atual' significa 'com processo AINDA EM TRAMITAÇÃO', não 'mandato vigente' — a lista mistura senadores, deputados e ex-parlamentares, e a mesma pessoa pode aparecer 2× com códigos distintos (ex.: como 'Senador' e como 'Deputado', pelo tratamento); não use como lista de senadores em exercício (para isso, senado_listar_senadores). Retorna { count, total, autores }, cada autor com codigo, nome, tratamento, uf e quantidadeMaterias. Filtros opcionais uf e nome (busca parcial sem acento); limite padrão 50 (máx. 1000). Use o codigo em senado_obter_senador ou senado_search_processos (codigoParlamentarAutor).

Input Schema

TableJSON Schema

Name	Required	Description
`uf`	No	Filtrar por UF (ex: SP)
`nome`	No	Filtrar por nome (busca parcial)
`limite`	No	Máximo de resultados (padrão: 50)

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"

Changed2 schema fields changedJun 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- 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 readOnly/idempotent/non-destructive, so the baseline is met there; the description adds genuinely non-obvious behavioral context: the counter-intuitive reading of 'atual' (em tramitação, not mandato vigente), the mixed population of the list, and possible duplicate rows for the same person under different `tratamento`. It does not cover pagination/truncation behavior beyond `limite`, which keeps it short of 5.

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 the semantic caveat, then return shape, then parameters — a sensible priority order with no filler. Dense, though the single long paragraph asks a fair amount of the reader at once.

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 goes further by naming the payload keys (`count`, `total`, `autores`) and per-author fields, and it resolves the biggest ambiguity an agent would face (the meaning of 'atual'). Nothing needed 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 coverage is 100%, so the baseline is 3, but the description adds real semantics beyond the schema: `nome` is accent-insensitive partial matching and `limite` defaults to 50 with a 1000 ceiling. The `uf` filter adds little over the schema's example.

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 precise verb+resource ('Lista parlamentares autores de processos em tramitação'), plus the ordering rule (by produção). It explicitly disambiguates itself from the sibling `senado_listar_senadores`, so an agent can pick the right tool without opening either 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?

Gives explicit when-to-use, an explicit when-NOT-to-use ('não use como lista de senadores em exercício'), names the alternative for that case, and explains downstream usage of the returned `codigo` in `senado_obter_senador` and `senado_search_processos`.

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.