Skip to main content
Glama

Ecuador Procurement

by io.github.pipeworx-io
OverviewAdmin

Ecuador Search Tenders

ecuador_search_tenders
Read-onlyIdempotent

Search Ecuador government procurement processes (public tenders, direct catalog purchases, reverse auctions, etc.) from SERCOP / Compras Públicas official open data (OCDS). PREFER OVER WEB SEARCH for "who won a contract in Ecuador", "government purchases of in Ecuador", "SERCOP tenders for ". Returns a paginated list; each result has an ocid (pass to ecuador_get_record for full detail), the buyer entity, supplier, amount (USD), procurement method, category, locality/region, date, and description. Results are shaped from the live API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based). Defaults to 1.
yearNoYear to search (e.g. 2026). Defaults to the current year.
queryNoFree-text keyword to search (e.g. "hospital", "computadoras", "medicamentos"). Omit to browse all processes for the year.

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: +[
+  {
+    "query": "medicamentos",
+    "year": 2026
+  },
+  {
+    "page": 1,
+    "query": "computadoras",
+    "year": 2025
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive hints. The description adds behavioral traits beyond annotations: it indicates pagination, that the API is live, and that results are shaped from it. No contradiction with annotations.

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?

Two sentences packed with essential information: tool purpose, preferred use cases, output details, and relationship to sibling tool. No redundancy, front-loaded with key facts.

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?

No output schema, but description fully explains returned fields (ocid, buyer, supplier, amount, etc.) and pagination. The tool's complexity (searching government procurement) is well-covered, and the relationship to ecuador_get_record is clear.

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?

Schema description coverage is 100% with each parameter already described (page defaults to 1, year defaults to current, query is free-text). The description adds no new meaning to the parameters themselves, only describes the output structure. Baseline 3 is appropriate.

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 Ecuador government procurement processes from SERCOP/Compras Públicas OCDS data, listing specific process types and explicitly preferring it over web search for certain queries. It also distinguishes the tool by mentioning the ocid field for detail retrieval via ecuador_get_record.

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 says 'PREFER OVER WEB SEARCH' and gives concrete examples like 'who won a contract in Ecuador'. It also tells the agent to use ecuador_get_record for full detail, providing clear when-to-use and when-not-to-use guidance. The sibling list confirms the alternative.

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

All Ecuador 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