Senado BR — Brazilian Federal Senate Open Data

Detalhar contratação

senado_contratacao_detalhe

Read-onlyIdempotent

Retrieve a specific section of a Brazilian Senate procurement contract by ID, choosing items, payments, guarantees, amendments, or activations. Returns raw records limited to 500, with totals and truncation alerts to inform further queries.

Instructions

Detalha uma seção específica de uma contratação já identificada pelo id. tipo indica a natureza do registro: contratos (contrato firmado; padrão), atas_registro_preco (compromisso de preços para compras futuras) ou notas_empenho (reserva orçamentária do gasto). secao escolhe o aspecto: itens, pagamentos, garantias (qualquer tipo), aditivos (só contratos) ou acionamentos (só atas_registro_preco). Retorna { id, tipo, secao, count, total, itens } com os registros brutos da seção (campos conforme a API administrativa), limitados a limite (padrão 100, máx 500) — count < total indica truncagem; seção sem registros retorna count 0 e itens vazio (o id é conferido na lista-pai antes, então count 0 significa mesmo seção vazia, não contratação inexistente); id que não existe e combinações secao×tipo inválidas (ex.: aditivos fora de contratos) retornam erro. Atenção: a fonte NÃO publica o valor do contrato em nenhuma seção; apenas aditivos traz valor, referente ao termo aditivo (às vezes nulo) — não procure valor monetário em itens/pagamentos/garantias. Obtenha o id via senado_contratos ou senado_contratacoes_lista — para localizar a contratação (não detalhá-la) use aquelas ferramentas.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ID da contratação (campo 'id' das listas de contratos/atas/empenhos)
`tipo`	No	contratos = contrato firmado (padrão); atas_registro_preco = compromisso de preços p/ compras futuras; notas_empenho = reserva orçamentária do gasto	contratos
`secao`	Yes	Aspecto a detalhar: itens/pagamentos/garantias (qualquer tipo); aditivos (só contratos); acionamentos (só atas_registro_preco)
`limite`	No	Máximo de itens (padrão 100, máx 500); count < total sinaliza corte

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

changedInput schema / properties / limite / description

Previous value: -"Máximo de itens (padrão: 100)"New value: +"Máximo de itens (padrão 100, máx 500); count < total sinaliza corte"

changedInput schema / properties / secao / description

Previous value: -"aditivos: apenas contratos; acionamentos: apenas atas"New value: +"Aspecto a detalhar: itens/pagamentos/garantias (qualquer tipo); aditivos (só contratos); acionamentos (só atas_registro_preco)"

changedInput schema / properties / tipo / description

Previous value: -"Tipo da contratação"New value: +"contratos = contrato firmado (padrão); atas_registro_preco = compromisso de preços p/ compras futuras; notas_empenho = reserva orçamentária do gasto"

changedOutput schema / $schema

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

Changed3 schema fields changedv3.3.3Jul 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
First observedv3.3.1Jun 25, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds substantial behavioral context beyond annotations: the source does not publish contract value, count < total indicates truncation, count 0 means an empty section rather than a missing contract, and invalid id or combinations return errors. 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?

Although lengthy, every sentence earns its place. The core purpose is front-loaded, followed by parameter semantics, edge cases, and sibling routing. The structure is logical and avoids redundancy, making it an efficient reference for an agent.

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?

The description covers the return format, truncation semantics, empty-section handling, error conditions, the absence of contract value, and how to obtain the id. Given the tool's complexity (multiple enums, combinations, edge cases) and that an output schema exists, the description is fully complete for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description adds significant meaning beyond the schema: it explains the semantic differences between tipo values (contratos, atas_registro_preco, notas_empenho), the constraints on secao per tipo, and the meaning of limite and count/total. This goes well beyond the schema's field descriptions.

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?

The description states a specific verb (detalha), resource (contratação), and scope (seção específica) and explicitly distinguishes itself from sibling tools by naming senado_contratos and senado_contratacoes_lista as alternatives for locating contracts. This makes it unmistakable what the tool does and what it does not.

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?

The description explicitly states when to use the tool (when you have an id and need a specific section) and when not to (to locate a contract, use the list tools). It also clarifies valid and invalid tipo×secao combinations, providing clear exclusions and alternatives.

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

Deploy Server