Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

by SidneyBissoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Orientação de bancada

senado_orientacao_bancada
Read-onlyIdempotent

Retrieve party leadership voting orientations in Brazilian Senate plenary sessions by date or period, including vote counts and party positions, to analyze party discipline.

Instructions

Orientação de bancada nas votações de plenário: como cada liderança partidária orientou o voto, com placar — essencial para análise de disciplina partidária. Retorna { count, votacoes }, com cada votação trazendo codigoVotacaoSve, descricao, materia, dataInicio, dataTermino, sessao, totais (totalSim, totalNao, totalAbstencao, obstrucoes), quorumInicial/quorumFinal e orientacoes (partido, voto). Informe data (um dia) ou o período dataInicio/dataFim. O codigoVotacaoSve é o identificador interno do sistema de votação eletrônica e pertence a um espaço de numeração próprio: NÃO serve como entrada de senado_obter_votacao (use a data com senado_search_votacoes para chegar ao código da votação). Para o resultado das sessões use senado_resultado_plenario.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoData da sessão (YYYYMMDD)
dataFimNoData fim do período (YYYYMMDD)
dataInicioNoData início do período (YYYYMMDD)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv3.3.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  3. First observedv3.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description goes beyond that by documenting the return contract (`{ count, votacoes }` with each vote's fields) and the important behavioral quirk that `codigoVotacaoSve` lives in an internal numbering space and is not interoperable with another tool.

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?

The description is front-loaded with purpose, then gives the return shape, then the key usage warnings and sibling routing. It is compact but fairly dense; the field list is useful but slightly long, though each sentence contributes to correct invocation.

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 query tool with annotations and a rich description, this is complete: it covers input modes, return fields, identifier semantics, and related tools. An agent has everything needed to decide when to call it and what to expect back.

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?

The input schema already covers 100% of parameters with formats and meanings. The description adds genuine value by specifying invocation modes — provide a single day via `data` or a range via `dataInicio`/`dataFim` — which the schema alone does not express as a usage rule.

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?

The description states a specific verb and resource: it returns how each party leadership oriented its vote in plenary votes, with a tally, explicitly serving party discipline analysis. It also distinguishes itself from related Senate tools by warning that `codigoVotacaoSve` cannot be used with `senado_obter_votacao` and that session results belong to `senado_resultado_plenario`.

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?

It explicitly tells the agent when to use this tool versus alternatives: use it for party discipline analysis, pass either `data` or `dataInicio`/`dataFim`, do not feed `codigoVotacaoSve` into `senado_obter_votacao`, and use `senado_search_votacoes` to reach the vote code. It also routes session-result queries to `senado_resultado_plenario`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools