Dados Abertos Senado BR MCP

Lideranças partidárias

senado_liderancas

Read-onlyIdempotent

Lista as lideranças do Senado, da Câmara e do Congresso Nacional (líderes, vice-líderes etc.). Retorna { count, liderancas }, cada item com tipo, descricao, unidadeLideranca, casa, dataDesignacao, dataTermino, numeroOrdemViceLider, bloco (codigo/nome/sigla — preenchido quando a liderança é de bloco; o codigo serve em senado_obter_bloco), partido (codigo/sigla/nome — a unidade liderada, quando liderança de partido) e parlamentar (codigo, nome, partido de filiação, uf). A fonte NÃO publica a UF do parlamentar (vem sempre null) — obtenha-a via senado_obter_senador pelo codigo. Filtre por casa (SF/CN/CD), codigoParlamentar, vigente (S/N) ou siglaTipoLideranca; sem filtros retorna todas as casas. Para a composição de blocos use senado_listar_blocos.

Input Schema

TableJSON Schema

Name	Required	Description
`casa`	No	Casa legislativa (SF=Senado, CN=Congresso, CD=Câmara dos Deputados)
`vigente`	No	Apenas vigentes (S/N)
`codigoParlamentar`	No	Código do parlamentar
`siglaTipoLideranca`	No	Tipo de liderança (ex: LIDER, VICE-LIDER)

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 16, 2026

changedInput schema / properties / casa / description

Previous value: -"Casa legislativa (SF=Senado, CN=Congresso)"New value: +"Casa legislativa (SF=Senado, CN=Congresso, CD=Câmara dos Deputados)"

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

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description goes well beyond by disclosing a real data caveat: the source never publishes the parliamentarian's UF (always null) and the agent must resolve it via senado_obter_senador. It also explains conditional field population (bloco filled only for bloc leaderships, partido only for party leaderships).

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 return shape, then filters, then alternatives — a logical order. It is dense and somewhat long, enumerating many fields that an output schema already carries, but each clause carries actionable information (field semantics, the UF null caveat, routing hints).

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?

For a read-only listing tool with an output schema, the description supplies everything an agent needs: return structure, conditional field meaning, filtering semantics, a known data-quality trap with its workaround, and sibling routing. Nothing material 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 value the schema lacks: it defines the default when no filters are supplied (all houses) and clarifies the casa abbreviations in context of filtering. It does not add syntax beyond the schema for codigoParlamentar or siglaTipoLideranca.

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 ("Lista") and resource ("lideranças") and scopes it precisely to Senate, Chamber and National Congress, with examples (líderes, vice-líderes). An agent immediately knows what entity is returned and can distinguish it from sibling list tools.

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 enumerates the four filter options (casa, codigoParlamentar, vigente, siglaTipoLideranca), states the default behavior (no filters returns all houses), and routes the agent to alternatives: senado_listar_blocos for bloc composition, senado_obter_bloco/senado_obter_senador for follow-up lookups.

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.