Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver reportes SITREP de un evento SGR

get_sgr_sitrep_archivos
Read-only

Retrieve national, provincial, and cantonal SITREP PDF links for a specific SGR event page URL; returns links, not contents.

Instructions

SITREP PDF links (national, provincial, cantonal) for one SGR event page from search_sgr_sitreps. Returns links, not contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
evento_urlYesAn event URL from search_sgr_sitreps's "url" field (must be on gestionderiesgos.gob.ec).

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 / evento_url / description
      Added value: +"An event URL from search_sgr_sitreps's \"url\" field (must be on gestionderiesgos.gob.ec)."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / evento_url / title
      Removed value: -"Evento Url"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / title
      Removed value: -"get_sgr_sitrep_archivosArguments"
    • removedOutput schema / title
      Removed value: -"get_sgr_sitrep_archivosDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so safety is covered. The description adds genuinely new behavioral context beyond the structured fields: the tool returns link references rather than document contents, which sets expectations about the response.

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 short sentences, zero filler, with the scope and return-type qualifier 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?

For a simple read-only link extractor with no output schema, the description covers what is returned and what is not. It does not mention the text/json format toggle, though the schema documents that parameter adequately.

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%, and the schema already documents both parameters, including that evento_url must come from search_sgr_sitreps and reside on gestionderiesgos.gob.ec. The description restates the source of evento_url, adding little beyond the schema, so the 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?

The description names a specific verb and resource ('SITREP PDF links... for one SGR event page') and scopes it (national, provincial, cantonal). It explicitly distinguishes itself from the sibling search_sgr_sitreps by stating the URL comes from that tool, and 'Returns links, not contents' separates it from read_pdf.

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?

It states the prerequisite source for the required argument ('from search_sgr_sitreps'), which is a clear when-to-use signal, and 'Returns links, not contents' implicitly routes the agent to read_pdf for actual content. No explicit when-not or exclusion is spelled out, keeping it just under a 5.

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