MCP Compras.gov.br

compras_contrato_comprasnet_consultar

Read-onlyIdempotent

Get full contract data from Comprasnet, including embedded sub-resources. CPFs are masked per LGPD, and results are cached for 15 minutes.

Instructions

Consulta detalhe completo de um contrato no Comprasnet (/api/contrato/id/{id}).

Devolve contrato com sub-recursos embutidos. CPFs mascarados por LGPD. Cache 15 min.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id_contrato": "<id_contrato>"
    },
    "name": "compras_contrato_comprasnet_consultar"
  }
}

Input Schema

Name	Required	Description	Default
`id_contrato`	Yes	ID interno do contrato no Comprasnet (pode ser diferente do id no Dados Abertos). Obtenha em `compras_contrato_comprasnet_por_uasg`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.14Aug 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds non-obvious context beyond annotations: embedded sub-resources, LGPD-masked CPFs, and a 15-minute cache.

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 three short, front-loaded sentences with no filler: operation, returned content, privacy note, and cache. Every sentence adds value.

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?

With one required parameter, a full schema description, rich annotations, and an output schema present, the description covers the remaining behavioral facts an agent needs, including LGPD masking, cache behavior, and embedded sub-resources. Nothing essential is missing.

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 description coverage is 100%, and the id_contrato schema description already explains that it is the internal Comprasnet ID, may differ from the Dados Abertos ID, and should be obtained from compras_contrato_comprasnet_por_uasg. The tool description itself adds no further parameter semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the exact operation: 'Consulta detalhe completo de um contrato no Comprasnet' and identifies the endpoint. The phrase 'sub-recursos embutidos' helps distinguish it from the many sibling sub-resource tools, though it does not explicitly name an alternative, so it stops short of a 5.

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

Usage Guidelines3/5

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

The description implies when to use it (when full contract detail is needed), and the schema usefully tells the agent to obtain the id from compras_contrato_comprasnet_por_uasg. However, it gives no explicit conditions for preferring this tool over the many contract-related siblings.

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

Deploy Server