Skip to main content
Glama
SidneyBissoli

Senado BR — Brazilian Federal Senate Open Data

by SidneyBissoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Detalhar bloco parlamentar

senado_obter_bloco
Read-onlyIdempotent

Fetch details of a Brazilian Senate parliamentary bloc by its code, including current and historical party composition.

Instructions

Obtém detalhes de um bloco parlamentar específico pelo seu código. Retorna um objeto com codigo, nome, nomeApelido, dataCriacao, dataExtincao e partidos (array com sigla, nome, dataAdesao, dataDesligamento); dataExtincao é null para blocos vigentes. partidos é a composição HISTÓRICA: quem tem dataDesligamento preenchida já saiu do bloco (composição atual = dataDesligamento null). Obtenha o parâmetro codigo primeiro via senado_listar_blocos; código inexistente retorna erro ("Bloco parlamentar não encontrado").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codigoYesCódigo do bloco parlamentar

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.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the safety profile is free. The description still adds real behavioral context beyond them: the exact error condition for a nonexistent code and the semantic rule that `partidos` is a HISTORICAL composition where a non-null `dataDesligamento` means the party has left.

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?

A single dense paragraph, front-loaded with the purpose and ending with the prerequisite and error behavior. The enumeration of return fields partially duplicates the output schema, which is the only slightly wasteful element.

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?

With an output schema present, the description need not restate return fields, yet it still supplies the interpretive nuance the schema cannot (null dataExtincao = active block, historical vs current party composition) plus the prerequisite and error path. 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?

Only one parameter with 100% schema coverage, so the baseline is 3. The description adds value above the schema by telling the agent how to source the value ('obtenha o parâmetro codigo primeiro via senado_listar_blocos'), which the schema cannot express.

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 ('Obtém detalhes') plus resource ('bloco parlamentar') and the lookup key ('pelo seu código'). It is immediately distinguishable from the sibling senado_listar_blocos, which enumerates rather than details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: obtain `codigo` first via `senado_listar_blocos`, and warns that an unknown code returns an error. It names the prerequisite sibling tool but does not spell out the inverse exclusion (e.g. 'do not use this to enumerate blocks'), so it falls just short of a full when/when-not statement.

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