Skip to main content
Glama
Sign In
EcuDataMCP

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Resumir las compras públicas de una institución (SERCOP)

get_resumen_compras
Read-only

Summarizes a buyer’s annual SERCOP procurement—process counts, total amounts, procedure types, monthly trends, and top suppliers—and flags when results are partial.

Instructions

Summarize one buyer's SERCOP procurement in a year: process count, total amount, by procedure type, by month and top suppliers. Reads up to 300 processes and says when the summary is partial.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "comprador": "<comprador>"
    },
    "name": "get_resumen_compras"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoYear of the processes (2015-current).
queryNoOptional topic keyword (min 3 chars) to narrow the processes; empty uses the buyer keyword.
formatNotext summary (default) or json structured result.text
compradorYesBuyer/institution keyword, min 3 chars (e.g. "Municipio de Quito", "IESS").

Output Schema

NameRequiredDescriptionDefault
filasNo
sourceNo
columnasNo
metadatosYes
url_fuenteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds the genuinely useful behavioral fact that it reads up to 300 processes and self-reports when the summary is partial. That truncation disclosure is exactly the kind of context annotations cannot carry. It does not mention latency, rate limits, or cost of a large scan, which keeps it short of a 5.

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, zero filler, and the substantive content (what is aggregated, then the 300-process cap and partial-result flag) is front-loaded. Every clause earns its place.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile; the description supplies the operational caveat about the 300-process ceiling. What remains thin is guidance on the comprador-versus-query interplay, though the schema largely compensates.

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%, so every parameter (year, query, format, comprador) is already documented with defaults, min-length constraints, and examples. The description only echoes the high-level notion of a buyer keyword and a yearly window, adding no syntax or precedence detail beyond the schema — baseline 3 applies.

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?

States a specific verb and resource ('Summarize one buyer's SERCOP procurement in a year') and enumerates exactly what is aggregated: process count, total amount, procedure type, month, and top suppliers. The SERCOP/procurement domain scoping cleanly separates it from the sibling resumen/indicador tools, which cover unrelated datasets.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the tool for a per-buyer yearly rollup, but there is no explicit when-to-use or when-not, and no guidance on choosing between a buyer-level scan and a narrower query (e.g., when to prefer a keyword-narrowed run). The 'partial summary' note hints at a tradeoff without telling the agent what to do about it.

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

Deploy Server

Other Tools