Skip to main content
Glama

Secop Buscar Contratos

secop_buscar_contratos
Read-onlyIdempotent

Search and filter SECOP II state contracts by dates, text, entity, department, or supplier to locate relevant public procurement records.

Instructions

Busca contratos estatales en SECOP II (datos.gov.co). Fechas en AAAA-MM-DD.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "secop_buscar_contratos"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNo
hastaNo
textoNo
limiteNo
paginaNo
nit_entidadNo
departamentoNo
documento_proveedorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing behavioral on top of that — nothing about pagination, default empty-string filter behavior, result caps, or how the external API responds.

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?

Two terse sentences with the core purpose front-loaded and the format rule second; nothing is padded. The terseness is a completeness problem, not a verbosity problem, so it scores well here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An 8-parameter search tool with zero schema coverage needs the description to map filters and pagination behavior, and it does not. The existing output schema excuses it from explaining return values, but the filter/pagination contract an agent must reason about is missing.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description carries the full burden and largely fails: it only clarifies the AAAA-MM-DD format for 'desde'/'hasta'. 'texto', 'limite', 'pagina', 'nit_entidad', 'departamento' and 'documento_proveedor' get no semantics, and the meaning of empty-string defaults is unstated.

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?

States a specific verb and resource ('Busca contratos estatales') plus the data source (SECOP II / datos.gov.co), which is more than the name alone. It does not, however, distinguish itself from the sibling 'secop_buscar_procesos', which sounds like the same act over a different resource.

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 gives no when-to-use guidance, no prerequisites, and no mention of any alternative tool for the same question. Only a date-format convention is offered, which is a parameter detail rather than usage guidance.

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