Skip to main content
Glama

Colombia Secop

by io.github.pipeworx-io
OverviewAdmin

Colombia Search Processes

colombia_search_processes
Read-onlyIdempotent

Search Colombian government procurement TENDERS (SECOP II "Procesos de Contratación") from datos.gov.co. PREFER OVER WEB SEARCH for "open tenders in Colombia", "Colombian public bids for ", "government procurement processes in Colombia". Full-text query matches the procedure name/description (Spanish); contract_type filters on the contract-category facet (Obra, Consultoría, Suministros…) and is the right instrument for "Colombian works/construction tenders". Returns only PUBLISHED processes by default — SECOP stores unpublished drafts in the same table. Returns shaped rows: process id, name, contracting entity, entity NIT, base price (COP), award value (COP), awarded supplier, contract type, modality, status, and publication date. Values are in Spanish as published.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return (1-1000, default 20).
queryNoKeyword(s) to full-text match against the procedure name/description, e.g. "software", "vías", "medicamentos". Spanish terms work best. Omit for most-recent tenders.
entityNoOptional — filter by contracting entity name (partial match), e.g. "DANE", "ALCALDIA".
_apiKeyNoOptional — your own Socrata app token (datos.gov.co) for higher rate limits. The endpoint is keyless: omit this and calls still work.
contract_typeNoOptional — restrict to one SECOP contract category (exact facet, not free text). Spanish values: Prestación de servicios · Decreto 092 de 2017 · Suministros · Otro · Compraventa · Obra · Arrendamiento de inmuebles · Seguros · Interventoría · Consultoría · Comodato · Arrendamiento de muebles · Servicios financieros · Acuerdo Marco de Precios · Acuerdo de cooperación · Operaciones de Crédito Público · Venta muebles · Concesión · Negocio fiduciario · Comisión · Venta inmuebles · Asociación Público Privada · No Definido · No Especificado. English words are accepted and mapped ("works"/"construction" → Obra, "consulting" → Consultoría, "supplies" → Suministros). Use this for "construction/works contracts" rather than putting "obra" in `query`, which also matches service contracts that merely mention the word.
include_unpublishedNoInclude draft processes that have no publication date (SECOP "Borrador"). Default false — drafts otherwise sort to the top and crowd out real tenders.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-colombia-secop-api-key",
-    "limit": 20,
-    "query": "software"
-  },
-  {
-    "_apiKey": "your-colombia-secop-api-key",
-    "entity": "ALCALDIA",
-    "limit": 10,
-    "query": "medicamentos"
-  }
-]New value: +[
+  {
+    "contract_type": "Obra",
+    "limit": 20
+  },
+  {
+    "entity": "ALCALDIA",
+    "limit": 10,
+    "query": "medicamentos"
+  }
+]
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Socrata app token (datos.gov.co) for higher rate limits. Omit to use the keyless endpoint."New value: +"Optional — your own Socrata app token (datos.gov.co) for higher rate limits. The endpoint is keyless: omit this and calls still work."
    • addedInput schema / properties / contract_type
      Added value: +{
+  "description": "Optional — restrict to one SECOP contract category (exact facet, not free text). Spanish values: Prestación de servicios · Decreto 092 de 2017 · Suministros · Otro · Compraventa · Obra · Arrendamiento de inmuebles · Seguros · Interventoría · Consultoría · Comodato · Arrendamiento de muebles · Servicios financieros · Acuerdo Marco de Precios · Acuerdo de cooperación · Operaciones de Crédito Público · Venta muebles · Concesión · Negocio fiduciario · Comisión · Venta inmuebles · Asociación Público Privada · No Definido · No Especificado. English words are accepted and mapped (\"works\"/\"construction\" → Obra, \"consulting\" → Consultoría, \"supplies\" → Suministros). Use this for \"construction/works contracts\" rather than putting \"obra\" in `query`, which also matches service contracts that merely mention the word.",
+  "type": "string"
+}
    • addedInput schema / properties / include_unpublished
      Added value: +{
+  "description": "Include draft processes that have no publication date (SECOP \"Borrador\"). Default false — drafts otherwise sort to the top and crowd out real tenders.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-colombia-secop-api-key",
+    "limit": 20,
+    "query": "software"
+  },
+  {
+    "_apiKey": "your-colombia-secop-api-key",
+    "entity": "ALCALDIA",
+    "limit": 10,
+    "query": "medicamentos"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Despite readOnly/idempotent/destructive annotations already covering the safety profile, the description reveals important non-obvious behavior: only PUBLISHED processes are returned by default because SECOP hides unpublished drafts in the same table, and return values are 'in Spanish as published.' It also lists the exact output without relying on an output schema, which gives the agent more confidence about what it will receive.

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 prose is dense and front-loaded: preference rule first, then scope, then filtering logic, then default behavior, then return shape, then language. Each sentence earns its place, and it stays focused without repeating verbosity beyond what is already in the schema.

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

Completeness4/5

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

For a read-only search tool with no output schema, the description does a lot of heavy lifting: it names the API domain, the concrete use case, the published/draft distinction, the Spanish language expectation, and the exact fields returned. The remaining gaps are minor, such as not explicitly handling result-size/pagination guidance beyond the `limit` parameter in the schema.

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?

The input schema covers all 6 parameters with detailed descriptions (limit default, query semantics, contract_type Spanish values, `include_unpublished` default, `_apiKey` optionality), so the baseline for this dimension is 3. The description does add some reinforcement around full-text `query` versus `contract_type`, but most of that same guidance is already in the schema description.

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 — 'Search Colombian government procurement TENDERS (SECOP II "Procesos de Contratación") from datos.gov.co' — so an agent can immediately identify what the tool returns. It does not explicitly draw a line against the sibling colombia_search_contracts, so it misses the full sibling-differentiation criterion for 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 Guidelines4/5

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

It explicitly tells the agent to 'PREFER OVER WEB SEARCH' for common Colombian procurement queries and gives clear field-selection guidance for `contract_type` (e.g., 'works/construction' → Obra). It does not provide a when-not-to-use statement or name the sibling tool as the alternative, though the usage guidance is otherwise strong.

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

All Colombia Secop toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources