Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

by SidneyBissoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Sessões do plenário

senado_encontro_plenario
Read-onlyIdempotent

Fetch a Brazilian Senate plenary session by its code. Choose details, agenda, results, or summary to view session data, scheduled items, voting outcomes, or an overview.

Instructions

Detalhes de um encontro legislativo (sessão de plenário). Retorna { codigo, secao, encontro }, onde encontro é o objeto bruto da API (ou array, quando o upstream traz vários) cujos campos variam conforme a secao escolhida: detalhes (padrão) traz dados gerais da sessão (tipo, data, situação, presença); pauta traz as matérias previstas; resultado traz os itens apreciados e seus resultados; resumo traz uma síntese. encontro pode vir vazio se a seção não tiver dados, e a chamada retorna erro se o codigo não existir. Obtenha o codigo via senado_agenda_plenario ou senado_resultado_plenario.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secaoNoQual seção do encontro consultardetalhes
codigoYesCódigo do encontro/sessão

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. Changed3 schema fields changedv3.3.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / codigo / maximum
      Added value: +9007199254740991
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  3. First observedv3.3.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive. Beyond that, the description discloses that encontro may be empty when a section has no data, that the call errors when the codigo does not exist, and that encontro's shape varies by section (object vs array). These are meaningful behavioral traits the annotations do not cover.

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 core purpose and return shape, then details sections, failure modes, and sourcing. It is dense and somewhat run-on within the long middle sentence, but every clause carries actionable information with no filler.

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 two-parameter read tool with an output schema, the description covers purpose, section semantics, return shape, empty-result behavior, error condition, and upstream sourcing. Nothing an agent needs 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% and both parameters are documented there, so a baseline of 3 applies. The description adds real meaning above the schema by spelling out what each enum value returns (detalhes general data, pauta planned items, resultado appreciated items, resumo synthesis) and where codigo comes from.

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 the specific resource (a legislative meeting / plenary session) and its scope, and explicitly contrasts the different data slices (detalhes/pauta/resultado/resumo). The named upstream siblings for obtaining the codigo make it clearly distinguishable from senado_agenda_plenario and 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?

Gives explicit routing: obtain the codigo via senado_agenda_plenario or senado_resultado_plenario, and explains which section to pick depending on the desired data. There is no when-not, but the preconditions and alternatives are concrete enough for correct invocation.

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