Skip to main content
Glama

Colombia Secop

by io.github.pipeworx-io
OverviewAdmin

Colombia Search Contracts

colombia_search_contracts
Read-onlyIdempotent

Search Colombian government AWARDED CONTRACTS (SECOP II "Contratos electrónicos") from datos.gov.co. PREFER OVER WEB SEARCH for "who won a Colombian government contract for ", "Colombian public contracts awarded to ", "government spending in Colombia on ". Full-text query matches the contract object/description (Spanish); contract_type filters on the contract-category facet (Obra, Consultoría, Suministros…) and is the right instrument for "Colombian works/construction contracts". Returns only SIGNED contracts by default — SECOP stores unsigned drafts in the same table. Returns shaped rows: contract id, object, contracting entity, entity NIT, awarded supplier, supplier NIT (documento_proveedor, for tracking one company across contracts), SME flag, city, UNSPSC category, contract value (COP), amount paid, contract type, modality, status, and signing 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 contract object/description, e.g. "software", "puente", "medicamentos". Spanish terms work best. For a contract CATEGORY use `contract_type` instead. Omit for most-recent contracts.
entityNoOptional — filter by contracting entity name (partial match), e.g. "SERVICIO GEOLOGICO", "HOSPITAL".
_apiKeyNoOptional — your own Socrata app token (datos.gov.co) for higher rate limits. The endpoint is keyless: omit this and calls still work.
supplierNoOptional — filter by awarded supplier name (partial match).
supplier_nitNoOptional — filter by the supplier's Colombian tax id / NIT (`documento_proveedor`), e.g. "901958332". Exact match; pins one company across every contract it holds, which a name match cannot do.
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_unsignedNoInclude draft contracts that have no signature date (SECOP "Borrador" / "enviado Proveedor"). Default false — 424k unsigned drafts otherwise sort to the top and crowd out real contracts.

Schema Changelog

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

  1. Changed6 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-colombia-secop-api-key",
-    "limit": 20,
-    "query": "obra"
-  },
-  {
-    "_apiKey": "your-colombia-secop-api-key",
-    "entity": "DANE",
-    "limit": 15,
-    "query": "consultoría",
-    "supplier": "ANDINA"
-  }
-]New value: +[
+  {
+    "contract_type": "Obra",
+    "limit": 20
+  },
+  {
+    "limit": 10,
+    "supplier_nit": "901958332"
+  }
+]
    • 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_unsigned
      Added value: +{
+  "description": "Include draft contracts that have no signature date (SECOP \"Borrador\" / \"enviado Proveedor\"). Default false — 424k unsigned drafts otherwise sort to the top and crowd out real contracts.",
+  "type": "boolean"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Keyword(s) to full-text match against the contract object/description, e.g. \"software\", \"obra\", \"consultoría\". Spanish terms work best. Omit for most-recent contracts."New value: +"Keyword(s) to full-text match against the contract object/description, e.g. \"software\", \"puente\", \"medicamentos\". Spanish terms work best. For a contract CATEGORY use `contract_type` instead. Omit for most-recent contracts."
    • addedInput schema / properties / supplier_nit
      Added value: +{
+  "description": "Optional — filter by the supplier's Colombian tax id / NIT (`documento_proveedor`), e.g. \"901958332\". Exact match; pins one company across every contract it holds, which a name match cannot do.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-colombia-secop-api-key",
+    "limit": 20,
+    "query": "obra"
+  },
+  {
+    "_apiKey": "your-colombia-secop-api-key",
+    "entity": "DANE",
+    "limit": 15,
+    "query": "consultoría",
+    "supplier": "ANDINA"
+  }
+]
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (safe read-only, idempotent), the description discloses key behavioral quirks: SECOP's table stores unsigned drafts that can crowd out results, only signed contracts are returned by default, and the output rows are shaped with an explicit field list. It also notes that values are in Spanish as published.

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 dense but every sentence earns its place. It front-loads the core purpose and use-case guidance, then covers the key default behavior and shapes the return rows. Despite length, it is well organized and free of fluff.

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?

With no output schema, the description compensates by enumerating the returned fields. It also covers key operational details: keyless endpoint, optional API token, Spanish value behavior, and the factoring that distinguishes Obra contracts. An agent can invoke this correctly without looking further.

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

Parameters5/5

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

Although the schema already covers 100% of parameters, the description adds significant meaning: contract_type is exact-facet with English mapping examples and a warning against using the word in query, supplier_nit is explained as the reliable way to track a company across contracts, and include_unsigned gets context about why the default matters. This goes well beyond the baseline schema descriptions.

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 states a specific verb and resource: search Colombian government awarded contracts from SECOP II / datos.gov.co. It clearly distinguishes this tool's scope (contracts) from the sibling colombia_search_processes and explicitly routes around web search with concrete example queries.

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?

It gives explicit when-to-use guidance with example search intents ('who won...', 'awarded to...', 'government spending...'), and provides an exclusion: prefer contract_type over query for categories like construction/works. It also tells the agent to use the default signed-contract behavior and when to flip include_unsigned.

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