Skip to main content
Glama

Dados Abertos Senado BR MCP

by io.github.SidneyBissoli
OverviewDiscussionsAdmin

Orçamento parlamentar (emendas)

senado_orcamento_parlamentar
Read-onlyIdempotent

Emendas parlamentares ao orçamento da União, conforme tipo (padrão emendas). tipo: emendas (proposição) → { tipo, count, emendas }, cada item (lote de emendas de um autor) com autor, codigoAutor, quantidadeEmendas, anoExecucao, materia (peça orçamentária, p.ex. LOA 29/2023), tipoPl, dataOperacao e ativo. tipo: oficios (execução — indicação de destino de emendas já aprovadas) → { tipo, ano, count, total, aviso?, oficios }, cada ofício com id, autor, protocolo, dataInclusao e quantidadeEmendas; filtre pelo ano do orçamento da emenda (recomendado — a base cobre vários anos), pagine com limite/pagina, e use incluirEmendas: true para o detalhe de cada emenda (favorecido, CNPJ, órgão, nota de empenho). Nota: no modo oficios, o ofício é o documento de execução que indica o destino do recurso de uma emenda já aprovada (posterior à proposição); a data do ofício difere do ano do orçamento. Para a execução do orçamento interno do próprio Senado (despesas/receitas) use senado_execucao_orcamentaria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anoNoAno do orçamento da emenda (filtra tipo=oficios pelo ano das emendas)
tipoNoemendas (lotes de emendas propostas) ou oficios (ofícios de indicação de destino)emendas
limiteNoMáximo de ofícios por página (tipo=oficios; padrão 50)
paginaNoPágina de ofícios (tipo=oficios; padrão 1)
incluirEmendasNotipo=oficios: incluir o detalhe das emendas (favorecido, CNPJ, nota de empenho)

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. Changed5 schema fields changed
    • addedInput schema / properties / ano
      Added value: +{
+  "description": "Ano do orçamento da emenda (filtra tipo=oficios pelo ano das emendas)",
+  "maximum": 2100,
+  "minimum": 1990,
+  "type": "integer"
+}
    • addedInput schema / properties / incluirEmendas
      Added value: +{
+  "default": false,
+  "description": "tipo=oficios: incluir o detalhe das emendas (favorecido, CNPJ, nota de empenho)",
+  "type": "boolean"
+}
    • addedInput schema / properties / limite
      Added value: +{
+  "default": 50,
+  "description": "Máximo de ofícios por página (tipo=oficios; padrão 50)",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / pagina
      Added value: +{
+  "default": 1,
+  "description": "Página de ofícios (tipo=oficios; padrão 1)",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / tipo / description
      Previous value: -"emendas (lotes de emendas) ou oficios (ofícios de apoio)"New value: +"emendas (lotes de emendas propostas) ou oficios (ofícios de indicação de destino)"
  4. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  5. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds non-obvious data behavior: the base spans multiple years so `ano` filtering is recommended, and that the ofício's date differs from the budget year of the emenda. It stops short of describing rate limits or pagination edge cases.

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 resource and its two modes before descending into per-mode return shapes, filtering and pagination guidance. It is dense and long, but every clause conveys operational detail (field names, mode semantics, year caveat) rather than filler; the single unbroken paragraph is the main structural weakness.

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?

Even though an output schema exists (so return values need not be described), the description covers mode semantics, the ano caveat, pagination, drill-down behavior and sibling routing. For a two-mode, five-parameter tool this leaves nothing an agent needs in order to call it correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds rationale the schema lacks: why `ano` should be set ('a base cobre vários anos') and what `incluirEmendas: true` actually surfaces (favorecido, CNPJ, órgão, nota de empenho). It also clarifies that `limite`/`pagina` only govern the oficios mode, going marginally beyond the schema text.

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 resource (emendas parlamentares ao orçamento da União) with two explicitly differentiated modes: emendas (proposição) and oficios (execução/indicação de destino). It names the sibling it is not ('Para a execução do orçamento interno do próprio Senado... use senado_execucao_orcamentaria'), so an agent can separate it from senado_execucao_orcamentaria 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?

Explains which mode to use (emendas = proposta, oficios = documento de execução posterior à proposição), recommends filtering by `ano` because 'a base cobre vários anos', and points to the correct alternative tool for internal Senate budget execution. When-to-use, mode selection and the alternative are all explicit.

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