Skip to main content
Glama
opedrosoares

MCP Compras.gov.br

by opedrosoares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

compras_contratacoes_14133_consultar

Read-onlyIdempotent

Retrieve complete procurement contract details under Brazilian law 14.133 by PNCP identifier. Get object, estimated value, modality, bidding notice, and status.

Instructions

Consulta uma contratação 14.133 pelo identificador.

Endpoint /modulo-contratacoes/1.1_consultarContratacoes_PNCP_14133_Id. Devolve detalhes completos: objeto, valor estimado, modalidade, instrumento convocatório, status no PNCP.

Aceita os dois identificadores do PNCP. Use tipo_identificador='idCompra' com o campo idCompra das listagens, ou 'numeroControlePNCPCompra' com o número de controle que aparece no edital (ex.: 10673078000120-1-000021/2025).

Cache 15 min.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_contratacaoYesIdentificador 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).
tipo_identificadorNoQual 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
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.17
    • 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"
+}
  2. First observedv0.3.14

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive traits, lowering the bar. The description adds the 15-minute cache behavior and the endpoint, which are useful beyond annotations. It does not contradict annotations, and the return content is hinted at with 'detalhes completos'.

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?

The description is well-structured and front-loaded with the purpose, then the endpoint and return details, then usage instructions. It's not overly long, and every sentence adds information. Could be slightly tighter but remains efficient.

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 low parameter count, high schema coverage, and presence of an output schema, the description covers all necessary usage aspects: identifiers, examples, and cache. It doesn't address not-found behavior, but that's likely covered by the output schema. Complete enough 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.

Parameters4/5

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

Schema coverage is 100% and both parameters have detailed descriptions, so the baseline is 3. The description adds extra value by providing concrete examples for each identifier format and the HTTP 500 note, which goes beyond the schema's descriptive 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?

The description clearly states it consults a 14.133 contract by identifier, lists the returned details (objeto, valor, modalidade, etc.), and names the endpoint. This distinguishes it from sibling tools like listar (list) and resultados (results) by focusing on single-record retrieval by ID.

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?

Explicitly explains the two accepted identifier formats and how to pass them via tipo_identificador, with concrete examples. It also notes the upstream rejects other values with HTTP 500, which is a practical caveat. It doesn't explicitly mention when not to use it, but the context is clear.

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

Deploy Server

Other Tools