MCP Compras.gov.br

compras_contratacoes_14133_resultados_por_contratacao

Read-onlyIdempotent

Retrieve contract award results for a specific procurement under Law 14.133 using either purchase ID or PNCP control number, with pagination support.

Instructions

Lista resultados (homologações) de uma contratação 14.133 específica.

Endpoint /modulo-contratacoes/3.1_consultarResultadoItensContratacoes.... Aceita idCompra ou número de controle PNCP, conforme tipo_identificador.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pagina`	No	Página de resultados (1-based). Padrão 1.
`id_contratacao`	Yes	Identificador da contratação. Aceita dois formatos, conforme `tipo_identificador`: o `idCompra` (17 dígitos, campo `idCompra` das listagens, ex.: '15813206001272025') ou o número de controle PNCP (alfanumérico com barra, campo `numeroControlePNCP`, ex.: '10673078000120-1-000021/2025' — é o número que aparece no edital).
`tamanho_pagina`	No	Quantidade de registros por página. Padrão 50, máximo 500.
`tipo_identificador`	No	Qual identificador está sendo passado em `id_contratacao`: 'idCompra' (padrão) ou 'numeroControlePNCPCompra'. O upstream rejeita qualquer outro valor com HTTP 500.	idCompra

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.17Sep 9, 2026

changedInput schema / properties / id_contratacao / description

Previous value: -"Identificador interno da contratação (campo `id` retornado em listar_contratacoes_14133)."New value: +"Identificador da contratação. Aceita dois formatos, conforme `tipo_identificador`: o `idCompra` (17 dígitos, campo `idCompra` das listagens, ex.: '15813206001272025') ou o número de controle PNCP (alfanumérico com barra, campo `numeroControlePNCP`, ex.: '10673078000120-1-000021/2025' — é o número que aparece no edital)."

changedInput schema / properties / id_contratacao / type
```
Previous value: -"integer"New value: +"string"
```

addedInput schema / properties / tipo_identificador

Added value: +{
+  "default": "idCompra",
+  "description": "Qual identificador está sendo passado em `id_contratacao`: 'idCompra' (padrão) ou 'numeroControlePNCPCompra'. O upstream rejeita qualquer outro valor com HTTP 500.",
+  "enum": [
+    "idCompra",
+    "numeroControlePNCPCompra"
+  ],
+  "type": "string"
+}

First observedv0.3.14Aug 18, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, and non-destructive behavior. The description adds no extra behavioral details such as error handling, rate limits, or side effects. The note about upstream rejecting invalid enum values is present in the parameter description (schema) rather than the main description, so it does not elevate the score.

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?

The description is concise, consisting of two sentences: the first states the purpose, the second mentions the endpoint and accepted identifiers. It is front-loaded and free of unnecessary detail, making it easy to parse quickly.

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?

Given the tool's complexity (4 parameters, 1 required) and full schema descriptions, the description provides sufficient context. It clarifies the resource and the flexible identifier options. The presence of an output schema further reduces the need for additional explanation, making the description adequately complete.

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

Parameters3/5

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

Schema descriptions cover 100% of parameters, providing detailed explanations including examples and defaults. The main description only summarizes the identifier types without adding new semantics. Since schema coverage is high, the baseline of 3 applies; the description adds marginal value.

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 clearly states the tool's purpose: it lists results (homologações) for a specific contract under law 14.133. The inclusion of 'de uma contratação específica' distinguishes it from broader listing tools like 'compras_contratacoes_14133_resultados_listar'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives. While the name and phrasing imply it is for a specific contract, it does not explicitly contrast with related tools (e.g., 'resultados_listar' or 'itens_por_contratacao'). No usage conditions or alternative recommendations are given.

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

Deploy Server