Skip to main content
Glama
juandavidsernav

secop-mcp-server

buscar_secop1

Search historical public procurement records from SECOP I for contracts prior to 2020. Use as fallback when SECOP II yields no results.

Instructions

Busca procesos de compra pública en SECOP I (datos históricos).

IMPORTANTE: SECOP I es el sistema ANTERIOR, ya NO se usa. Busca primero en SECOP II (buscar_procesos_secop2 o buscar_contratos_secop2). Solo usa esta herramienta si no encontraste resultados en SECOP II o si el contrato es anterior a ~2020.

Todos los filtros son opcionales y combinables entre sí (operador AND).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entidadNo
contratistaNo
identificacion_contratistaNo
numero_procesoNo
numero_contratoNo
objetoNo
departamentoNo
modalidadNo
estadoNo
cuantia_minimaNo
fecha_desdeNo
fecha_hastaNo
busqueda_textoNo
limiteNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that data is historical and system no longer used, and that filters are AND combinable. However, it does not mention any side effects, rate limits, or data freshness. For a search tool, this is adequate but not comprehensive.

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 short, front-loaded with purpose, includes critical usage guidance, and has no unnecessary words. Every sentence adds value.

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?

With 15 parameters, no schema descriptions, and no annotations, the description is insufficient to fully understand parameter semantics (e.g., valid values for 'modalidad', meaning of 'estado'). The existence of output schema does not cover parameter meaning. The description missing details for many parameters.

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 has 15 parameters with 0% description coverage. The description only states 'All filters are optional and combinable (AND)', which is a general note but does not explain each parameter's meaning. Given the low coverage, the description should compensate but fails to do so.

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 the tool searches public procurement processes in SECOP I (historical data), and distinguishes it from siblings by explicitly mentioning it is the older system and advising to use SECOP II first.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool (only if no results in SECOP II or contract is before ~2020) and directs to use SECOP II tools (siblings) first.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/juandavidsernav/secop-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server