Skip to main content
Glama

Secop Buscar Procesos

secop_buscar_procesos
Read-onlyIdempotent

Search SECOP II public contracting processes—tenders and calls—by keyword or entity NIT to find relevant Colombian procurement opportunities, with pagination and result limits.

Instructions

Busca procesos de contratación (licitaciones, convocatorias) en SECOP II.

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_procesos"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoNo
limiteNo
paginaNo
nit_entidadNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds nothing beyond them: no mention of pagination behavior, result ordering, dataset scope, or rate/coverage limits for an open-world search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with zero padding, which is concise, but the size is achieved by omission rather than by front-loading useful information. There is no structure beyond the single clause.

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?

For a paginated, open-world search over a national procurement dataset, the definition is too thin: pagination, filtering by entity NIT, and free-text matching semantics are undocumented, and no guidance is given on how results relate to sibling tools. The presence of an output schema covers return values, but little else is addressed.

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%, so the schema carries no meaning for the four parameters (texto, limite, pagina, nit_entidad). The parameter names are suggestive (free text, page size, page number, entity NIT), but the description supplies no semantics at all, leaving the agent to infer defaults, expected formats, and empty-string fallbacks.

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 a specific verb ('Busca') and resource ('procesos de contratación (licitaciones, convocatorias) en SECOP II'), which is enough to distinguish it from sibling secop_buscar_contratos at a coarse level. It stops short of explicitly contrasting the two, so an agent must infer the diferencia between procesos and contratos.

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?

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as secop_buscar_contratos or procesos_actuaciones. The agent must guess which SECOP search tool applies to a given request.

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