Skip to main content
Glama
Sign In
MCP Compras.gov.br

MCP Compras.gov.br

by opedrosoares
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

compras_contrato_ocorrencias

Read-onlyIdempotent

Retrieve contract occurrences and penalties to assess supplier reliability. Use contract ID to list sanctions and evaluate vendor trustworthiness.

Instructions

Lista ocorrências/penalidades (/api/contrato/{id}/ocorrencias).

Indicador-chave da confiabilidade do fornecedor. Paginação client-side. 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_ocorrencias"
  }
}

Input Schema

NameRequiredDescriptionDefault
paginaNoPágina de resultados (1-based). Padrão 1.
id_contratoYesID do contrato no Comprasnet.
tamanho_paginaNoQuantidade de registros por página. Padrão 50, máximo 500.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.14

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already cover read-only/idempotent behavior, and the description adds valuable behavior beyond them: client-side pagination and a 15-minute cache. These are practical operational caveats that help an agent invoke the tool correctly.

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 compact and front-loaded: purpose, usage signal, pagination, and cache are covered in a few short lines without filler. Every sentence contributes distinct information.

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?

Given the read-only/idempotent annotations, fully documented parameters, and presence of an output schema, this description is complete enough for safe invocation. The cache and pagination notes cover the main non-obvious calling conventions.

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?

All three parameters are already fully documented in the input schema (100% coverage), so the description is not expected to re-explain them. The pagination note adds some behavioral color but does not need to add schema-level parameter semantics.

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 opens with a specific verb and resource ("Lista ocorrências/penalidades") and gives the endpoint route, so the tool's purpose is clear. It does not explicitly call out how it differs from related sibling tools such as compras_checar_sancoes_fornecedor, leaving some distinction to inference.

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?

"Indicador-chave da confiabilidade do fornecedor" supplies useful usage context, but it does not say when to use this tool over the related sanctions/supplier tools or state when not to use it. The guidance is adequate but implicit.

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