Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar informes de situación (SITREP) del SGR

search_sgr_sitreps
Read-only

Search Ecuador's SGR adverse-event dossiers (2016–2026) by text or status, then retrieve linked situation report PDFs for earthquakes, floods, fires, or volcanic events.

Instructions

SGR's archive of ~54 adverse-event dossiers 2016-2026 (earthquakes, rainy and fire seasons, volcanic activity) with status. Next: get_sgr_sitrep_archivos(evento_url) for the SITREP PDFs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched (accent-insensitive) against the event's titulo, estado, or descripcion, e.g. "terremoto", "en curso", "manabi".
formatNotext summary (default) or json structured result.text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / query / description
      Added value: +"Free text matched (accent-insensitive) against the event's titulo, estado, or descripcion, e.g. \"terremoto\", \"en curso\", \"manabi\"."
  2. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_sgr_sitrepsArguments"
    • removedOutput schema / title
      Removed value: -"search_sgr_sitrepsDictOutput"
  3. First observedv0.8.12

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real value beyond them: archive size (~54), temporal coverage (2016-2026), event taxonomy, and the presence of a status field. No auth, rate limit, or pagination notes, but the archive characterization is substantive.

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 tight sentences, zero padding. The scope is front-loaded and the follow-up tool is placed last as a natural next step.

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?

An output schema exists, so return values need not be explained, and the description covers scope, content, and the follow-up workflow. For a 0-required-param search tool this is nearly complete; only an explicit alternative-routing statement is missing.

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% – both the query (accent-insensitive match against titulo/estado/descripcion, with examples) and format enum are fully documented in the schema. The description adds no parameter detail, so the baseline 3 applies.

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 the resource precisely: SGR's archive of ~54 adverse-event dossiers 2016-2026 with status, enumerating event categories (earthquakes, rainy/fire seasons, volcanic activity). This is a specific, informative scope rather than a tautology. It stops just short of naming the sibling it competes with (e.g. search_eventos_riesgo), so it earns a 4 rather than a 5.

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?

Gives clear forward-routing guidance: 'Next: get_sgr_sitrep_archivos(evento_url) for the SITREP PDFs', telling the agent what to do after this search. It does not specify when to prefer this over alternatives like search_eventos_riesgo or the contraloria/IESS dossiers, so no exclusions are stated.

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