Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

by SidneyBissoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Reuniões de comissão

senado_reunioes_comissao
Read-onlyIdempotent

Find Brazilian Senate committee meetings by acronym and date range. Returns list with code, description, date, time, location, type, and status.

Instructions

Lista reuniões de uma comissão (pela sigla) num intervalo dataInicio/dataFim (YYYYMMDD); sem datas, usa os últimos 14 dias. Atenção: o upstream devolve a agenda de TODAS as comissões do período (o filtro por sigla é local), então janelas amplas (mensais/anuais) podem estourar o limite de tamanho da resposta (erro de payload): prefira janelas de até 2 semanas e divida períodos maiores em chamadas sucessivas. Retorna { sigla, periodo, count, reunioes }, cada reunião com codigo, descricao, data, hora, local, tipo e situacao. Intervalos entre anos são divididos por ano internamente. Descubra a sigla via senado_listar_comissoes; use o codigo retornado em senado_reuniao_comissao para os detalhes da pauta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siglaYesSigla da comissão
dataFimNoData fim (YYYYMMDD)
dataInicioNoData início (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.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavioral context on top: the default 14-day window when dates are omitted, the fact that the upstream returns all committees and the sigla filter is applied locally, the resulting payload-size error risk, and internal per-year splitting. That is exactly the operational detail annotations cannot convey.

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?

Purpose and scoping come first, then the payload-limit warning, then the return shape and cross-tool routing — well front-loaded with no filler. It is a dense single paragraph, so a reader must parse several clauses to extract the window-size rule, but every sentence carries information.

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?

Covers the default window, the local-filter pitfall, the error mode and mitigation, cross-year handling, and cross-tool discovery/routing. With an output schema present it did not need to enumerate return fields, yet doing so costs nothing and reinforces the codigo handoff to senado_reuniao_comissao.

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 schema already documents all three parameters (baseline 3). The description adds real meaning beyond it: the YYYYMMDD format reminder, the omitted-date default of the last 14 days, and the crucial note that sigla filtering happens client-side rather than upstream.

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 ('Lista reuniões de uma comissão') scoped by sigla and a date range, and explicitly names the two sibling tools it relates to (senado_listar_comissoes for the sigla, senado_reuniao_comissao for details). An agent can place it among the ~60 siblings without opening any 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 routing: discover the sigla via senado_listar_comissoes and feed the returned codigo into senado_reuniao_comissao for agenda details. It also states a when-to-split rule (windows ≤2 weeks) and what to do for longer periods, leaving nothing to inference.

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