Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver el Resumen de Indicadores anual de SIPA

get_sipa_resumen_indicadores
Read-only

Retrieve monthly PDF links to SIPA's Resumen de Indicadores for a chosen year (2018 onward) to access Ecuadorian agricultural indicator reports.

Instructions

Monthly PDF links of SIPA's (MAG) "Resumen de Indicadores" for one year, 2018 onward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioYesYear, e.g. 2025.
formatNotext summary (default) or json structured result.text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Year, e.g. 2025."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / title
      Removed value: -"get_sipa_resumen_indicadoresArguments"
    • removedOutput schema / title
      Removed value: -"get_sipa_resumen_indicadoresDictOutput"
  4. First observedv0.8.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds that the return is a set of monthly PDF *links* (not embedded data) and that coverage starts in 2018, which is genuine context beyond the annotations, but it says nothing about pagination or whether a download step follows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the resource and scope front-loaded; zero filler. It is arguably too terse for the amount of behavior an agent must infer, but as pure structure it is efficient.

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

Completeness3/5

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

For a link-listing tool with no output schema, the description conveys what is returned and the year floor, which covers the essentials. It stops short of explaining how the linked PDFs are subsequently retrieved (e.g. via a download sibling) or the response shape, leaving the hub-and-spoke flow implicit.

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 coverage is 100%, so both parameters are already documented, making 3 the baseline. The description adds one meaningful constraint not in the schema ('2018 onward' bounds on 'anio'), but does not elaborate on the format enum's effect.

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?

States a specific resource ('SIPA's (MAG) Resumen de Indicadores') and the exact content returned ('Monthly PDF links'), with a scope qualifier ('for one year, 2018 onward'). It is clear enough that an agent can distinguish it from archive-listing siblings, though it never names an alternative directly.

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

Usage Guidelines2/5

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

The description reports the 2018-onward coverage boundary but gives no guidance on when to pick this tool versus the many other archive/indicator siblings, and no prerequisites or exclusions. An agent must infer usage purely from the resource name.

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