Skip to main content
Glama

Chile Procurement

by io.github.pipeworx-io
OverviewAdmin

Chile Search Tenders

chile_search_tenders
Read-onlyIdempotent

Search Chile government procurement tenders (licitaciones) from Mercado Público / ChileCompra, the official Chilean public-procurement platform. By default returns tenders published TODAY. Pass estado="activas" for all currently OPEN tenders, or fecha="ddmmyyyy" (e.g. "01072026") for tenders published on a specific day. Returns each tender's código (CodigoExterno), name, status, and closing date. Use chile_get_tender with a código for full detail (buyer, amount, line items).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fechaNoOptional publication date in ddmmyyyy format (e.g. "01072026" for 1 July 2026). Omit for today. Mutually exclusive with estado — if both given, fecha wins.
limitNoMax tenders to return (default 25, max 200). The result count column reflects the full API total.
estadoNoOptional tender-status filter. Use "activas" for all currently open tenders. Other accepted values include "publicada", "cerrada", "desierta", "adjudicada", "revocada", "suspendida". Omit for today's tenders.
keywordNoOptional keyword filter matched against the tender NAME. Tender names are in SPANISH — pass Spanish terms, translating if the user asked in another language (trucks → "camion", ambulance → "ambulancia", software licences → "licencias"). Multi-word input matches tenders containing ALL words in any order. Accent- and case-insensitive, and matches word stems, so "camion" also finds "CAMIONES".

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "estado": "activas",
+    "limit": 50
+  },
+  {
+    "keyword": "camiones",
+    "limit": 25
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / keyword
      Added value: +{
+  "description": "Optional keyword filter matched against the tender NAME. Tender names are in SPANISH — pass Spanish terms, translating if the user asked in another language (trucks → \"camion\", ambulance → \"ambulancia\", software licences → \"licencias\"). Multi-word input matches tenders containing ALL words in any order. Accent- and case-insensitive, and matches word stems, so \"camion\" also finds \"CAMIONES\".",
+  "type": "string"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations include readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, and the description fully aligns with these. It adds valuable behavioral details: return fields (código, name, status, closing date), keyword matching specifics (Spanish, accent-insensitive, stemming), and mutual exclusivity of fecha and estado. No contradictions.

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 four concise sentences, front-loaded with the primary purpose. Every sentence adds essential information without redundancy. It is well-structured for quick parsing by an AI agent.

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?

Given the tool has 4 optional parameters, no required parameters, and no output schema, the description fully covers usage: default behavior, parameter combinations, filtering logic, and a pointer to the detail tool. It is complete for an AI agent to select and invoke correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds significant value by explaining defaults (today), keyword behavior (Spanish, stemming), mutual exclusivity, and providing examples. This goes beyond schema descriptions, justifying a 4.

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 specifies the verb 'Search' and the resource 'Chile government procurement tenders (licitaciones) from Mercado Público / ChileCompra'. It explicitly distinguishes from the sibling tool 'chile_get_tender', which is used for full detail. This meets the highest standard of purpose clarity.

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?

The description provides concrete usage instructions: default returns today's tenders, use estado='activas' for open tenders, use fecha for a specific day, and use chile_get_tender for details. It explains keyword filtering in Spanish with accent-insensitivity and stemming. While it lacks explicit 'when not to use' statements, the guidance is clear and actionable.

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

All Chile Procurement 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