Senado BR — Brazilian Federal Senate Open Data

Listar contratações

senado_contratacoes_lista

Read-onlyIdempotent

List Brazilian Senate procurement records: price registration agreements, expense notes, or young apprentices. Supports text filter, sorting, and pagination, returning count and matching records.

Instructions

Lista, conforme tipo, atas de registro de preço, notas de empenho ou menores aprendizes do Senado, com filtro textual opcional aplicado no Worker sobre todos os campos. Retorna { tipo, count, total, registros }; para atas_registro_preco/notas_empenho cada registro segue o formato de contrato (id, numero, objeto, empresa, subEspecie, vigencia...), enquanto menores_aprendizes vêm como registros brutos da API (campos não normalizados). Ordenação por ordem sobre a sequência de id do upstream: desc (padrão) = mais recentes primeiro, asc = mais antigos primeiro; offset pula registros para paginar a cauda. Limitado a limite (padrão 50, máx 500), com aviso ao truncar; tipo sem registros retorna lista vazia. Para aprofundar uma ata/empenho, use o id em senado_contratacao_detalhe.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tipo`	Yes	Qual lista consultar
`ordem`	No	desc = mais recentes primeiro (padrão); asc = mais antigos primeiro (ordem de id do upstream)	desc
`filtro`	No	Filtro textual (empresa, objeto, etc.)
`limite`	No	Máximo de resultados (padrão: 50)
`offset`	No	Registros a pular após a ordenação (paginação; padrão: 0)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv3.9.0Sep 24, 2026

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
```

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Registros a pular após a ordenação (paginação; padrão: 0)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / ordem

Added value: +{
+  "default": "desc",
+  "description": "desc = mais recentes primeiro (padrão); asc = mais antigos primeiro (ordem de id do upstream)",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv3.3.3Jul 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
First observedv3.3.1Jun 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, but the description adds substantial context: return shape, per-tipo normalization differences, ordering semantics, truncation warning, empty-list behavior, and routing to detail. No contradiction with annotations.

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

Conciseness5/5

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

Front-loaded with purpose and return shape, then covers ordering, pagination, limits, and routing in a single dense paragraph. Every clause appears to earn its place, with no filler.

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 5-parameter read-only list tool with an output schema and rich annotations, the description covers return shape, per-tipo quirks, ordering, pagination, truncation, empty results, and escalation to detail. Nothing material for correct invocation 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?

Schema description coverage is 100%, so the schema already documents each parameter, making 3 the baseline. The description adds meaning beyond the schema by explaining that the textual filter is applied in the Worker over all fields, that tipo changes the record format, that offset paginates the tail after ordering, and that limite truncation triggers an aviso.

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 ('Lista') and resource (atas de registro de preço, notas de empenho, menores aprendizes) and distinguishes itself from the detail sibling by directing deeper lookups to senado_contratacao_detalhe. An agent can identify the tool's scope immediately.

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?

Routes the agent to senado_contratacao_detalhe for deepening an ata/empenho and explains ordering, filtering, and pagination context. However, it does not explicitly compare this tool with other list-oriented siblings such as senado_contratos or senado_licitacoes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server