Skip to main content
Glama

Dados Abertos Senado BR MCP

by io.github.SidneyBissoli
OverviewDiscussionsAdmin

Pesquisar processos

senado_search_processos
Read-onlyIdempotent

Busca processos legislativos no endpoint v3 /processo (parâmetros complementares ao senado_buscar_materias). Retorna { count, total, aviso?, processos }, cada item com id, codigoMateria, identificacao, ementa, tipoDocumento, dataApresentacao, autoria (compactada: primeiros autores + total), totalAutores, tramitando (boolean) e normaGerada. É obrigatório ao menos um filtro (sigla, número, ano, autor ou período). Limitado a limite (padrão 20, máx. 200), com aviso ao truncar. Use o id retornado em senado_obter_processo para detalhes. Ex.: { sigla: 'PL', ano: 2025, dataInicioApresentacao: '2025-03-01' } (datas em YYYYMMDD ou ISO).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anoNoAno do processo
autorNoNome do autor
siglaNoSigla do tipo de processo (ex: PL, PEC)
limiteNoMáximo de resultados (padrão: 20)
numeroNoNúmero do processo
tramitandoNoEm tramitação (S/N)
dataFimApresentacaoNoData fim da apresentação (YYYYMMDD ou YYYY-MM-DD)
codigoParlamentarAutorNoCódigo do parlamentar autor
dataInicioApresentacaoNoData início da apresentação (YYYYMMDD ou YYYY-MM-DD)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • 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"
  3. Changed1 schema field changed
    • addedInput schema / properties / limite
      Added value: +{
+  "default": 20,
+  "description": "Máximo de resultados (padrão: 20)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / dataInicioApresentacao / description
      Previous value: -"Data início da apresentação (YYYYMMDD ou YYYY-MM-DD; janela máxima de 1 ano)"New value: +"Data início da apresentação (YYYYMMDD ou YYYY-MM-DD)"
  5. Changed8 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / ano / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / ano / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / codigoParlamentarAutor / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / codigoParlamentarAutor / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / numero / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / numero / minimum
      Added value: +-9007199254740991
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world; the description adds the mandatory-filter constraint, the 200 cap with a truncation 'aviso', and the compacted autoria behavior. These are meaningful behaviors not visible in annotations or schema. It does not explain the weekday/format handling beyond dates, but overall it adds real value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and constraint well, but the middle sentence is a dense enumeration of every return field, which is redundant given an output schema exists. Format guidance and example are useful but the field list bloats the description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the mandatory-filter rule, pagination truncation, date formats, and sibling routing – enough for an agent to call correctly. An output schema exists so return-value explanations aren't required; the list of returned fields is a minor completeness trade-off rather than a gap.

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 already 100%, so baseline is 3. The description adds the required-at-least-one-filter rule (a semantic constraint no single parameter documents), the 20 default / 200 max for limite, the date format options (YYYYMMDD or ISO), and a worked example. That exceeds the schema baseline.

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 (Busca) and resource (processos legislativos) and explicitly scopes to the v3 /processo endpoint with complementary parameters to senado_buscar_materias. An agent can distinguish it from the sibling search tool without opening either 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?

Explicitly states the mandatory condition (at least one filter among sigla, número, ano, autor, or período), names the sibling it complements, and routes to senado_obter_processo for details. Nothing is left to inference.

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 toolsInspect
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.

Resources