Dados Abertos Senado BR MCP

Horas extras de servidores

senado_horas_extras

Read-onlyIdempotent

Horas extras pagas a servidores do Senado em ano/mes de referência (a partir de 2013). Para perguntas de maior/menor/média/mediana/distribuição/ranking ('quem recebeu mais horas extras', 'valor mediano de hora extra', 'distribuição dos pagamentos') use estatisticas=true: computa min/máx/média/mediana/desvio/percentis sobre TODAS as linhas filtradas (valorTotal) e devolve top/bottom (padrão 10) com identificadores. Sem agruparPor → distribuicao das linhas individuais + top/bottom; com agruparPor (nome/competencia) → grupos[] ranqueados por soma decrescente (grupos[0] = quem mais recebeu; por nome soma as linhas do mesmo servidor no mês), cada um com sua mini-distribuição. Sem estatisticas: retorna { ano, mes, count, total, valorTotal, horasExtras[] }, onde valorTotal soma o gasto do mês e cada item traz nome, valorTotal, horasExtras, competencia e pagamento. Filtro opcional por nome (busca parcial) e limite (padrão 100, máx 500; ignorado quando estatisticas=true). Para a remuneração completa do servidor use senado_remuneracoes_servidores.

Input Schema

TableJSON Schema

Name	Required	Description
`ano`	Yes	Ano de referência
`mes`	Yes	Mês de referência
`nome`	No	Nome do servidor (busca parcial)
`topN`	No	Tamanho das listas top/bottom quando estatisticas=true sem agruparPor (padrão: 10, máx: 100)
`limite`	No	Máximo de resultados (padrão: 100; ignorado quando estatisticas=true)
`agruparPor`	No	Quando estatisticas=true, ranqueia os grupos por soma decrescente (grupos[0] = quem mais recebeu): `nome` soma as linhas do mesmo servidor no mês, `competencia` agrupa por mês de prestação. Cada grupo traz sua mini-distribuição
`estatisticas`	No	Computa estatísticas (min/máx/média/mediana/percentis) + ranking top/bottom sobre todas as linhas filtradas. Use para 'quem recebeu mais/menos', 'média', 'mediana', 'ranking'

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedAug 31, 2026

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"

Changed4 schema fields changedJul 8, 2026

addedInput schema / properties / agruparPor

Added value: +{
+  "description": "Quando estatisticas=true, ranqueia os grupos por soma decrescente (grupos[0] = quem mais recebeu): `nome` soma as linhas do mesmo servidor no mês, `competencia` agrupa por mês de prestação. Cada grupo traz sua mini-distribuição",
+  "enum": [
+    "nome",
+    "competencia"
+  ],
+  "type": "string"
+}

addedInput schema / properties / estatisticas

Added value: +{
+  "default": false,
+  "description": "Computa estatísticas (min/máx/média/mediana/percentis) + ranking top/bottom sobre todas as linhas filtradas. Use para 'quem recebeu mais/menos', 'média', 'mediana', 'ranking'",
+  "type": "boolean"
+}

changedInput schema / properties / limite / description

Previous value: -"Máximo de resultados (padrão: 100)"New value: +"Máximo de resultados (padrão: 100; ignorado quando estatisticas=true)"

addedInput schema / properties / topN

Added value: +{
+  "default": 10,
+  "description": "Tamanho das listas top/bottom quando estatisticas=true sem agruparPor (padrão: 10, máx: 100)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

Changed2 schema fields changedJun 28, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedJun 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedJun 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds substantial behavioral context the annotations cannot: the two distinct response shapes, that valorTotal sums the month's spend, and that estimated ranking semantics apply via agruparPor. It does not mention rate limits or failure modes, keeping it just short of a 5.

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-loaded with purpose before branching into the estatisticas behavior, and every clause carries information. It is dense and somewhat run-on, but nothing is wasted; a minor trim would improve readability without losing content.

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 7-parameter tool with an output schema, this covers purpose, mode selection, filtering, pagination, and cross-tool routing. The two distinct return shapes are explained even though the output schema exists, leaving no ambiguity for correct invocation.

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 baseline is 3, but the description goes beyond restating fields: it clarifies that limite is ignored under estatisticas=true, that topN governs top/bottom when estatisticas=true without agruparPor, and elaborates the agruparPor ranking result. This adds interaction meaning the schema fields alone leave implicit.

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 (overtime pay to Senate servants) with scope (ano/mes de referência, a partir de 2013) and explicitly distinguishes itself from senado_remuneracoes_servidores, which covers full remuneration. An agent can tell exactly what this returns without opening the 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 routing: for max/min/mean/median/distribution/ranking questions use estatisticas=true, with concrete example phrasings ('quem recebeu mais horas extras'). It also names the alternative tool for full remuneration, so when-to-use and when-not-to-use are both covered.

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 tools Inspect

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.