Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar eventos de riesgo del SGR

search_eventos_riesgo
Read-only

Retrieve current and recent SGR risk events—landslides, floods, structural damage—from Ecuador's live COE feed, including location, status, and impacts.

Instructions

Current and recent SGR (Gestión de Riesgos) risk events from the live COE feed: landslides, floods, structural damage, with location, status and impacts. No history; for past event dossiers use search_sgr_sitreps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax events to return (default 15, max 100)
queryNoFree text (sector, cause, description keywords)
cantonNoCanton filter (e.g. "Quito")
estadoNoStatus filter (e.g. "Seguimiento", "Cierre")
eventoNoEvent type filter (e.g. "Deslizamiento", "Inundación", "Aluvión")
formatNotext summary (default) or json structured result.text
provinciaNoProvince filter (e.g. "Pichincha")

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. Changed7 schema fields changedv0.10.0
    • addedInput schema / properties / canton / description
      Added value: +"Canton filter (e.g. \"Quito\")"
    • addedInput schema / properties / estado / description
      Added value: +"Status filter (e.g. \"Seguimiento\", \"Cierre\")"
    • addedInput schema / properties / evento / description
      Added value: +"Event type filter (e.g. \"Deslizamiento\", \"Inundación\", \"Aluvión\")"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max events to return (default 15, max 100)"
    • addedInput schema / properties / provincia / description
      Added value: +"Province filter (e.g. \"Pichincha\")"
    • addedInput schema / properties / query / description
      Added value: +"Free text (sector, cause, description keywords)"
  3. Changed9 schema fields changedv0.8.14
    • removedInput schema / properties / canton / title
      Removed value: -"Canton"
    • removedInput schema / properties / estado / title
      Removed value: -"Estado"
    • removedInput schema / properties / evento / title
      Removed value: -"Evento"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / provincia / title
      Removed value: -"Provincia"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_eventos_riesgoArguments"
    • removedOutput schema / title
      Removed value: -"search_eventos_riesgoDictOutput"
  4. First observedv0.8.12

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the bar is lower. The description still adds real behavioral context: the data comes from a live COE feed, is current/recent only, and has no history. It stops short of describing pagination or refresh/rate behavior.

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 dense sentences, front-loaded with scope and content, then the disambiguation. No filler; 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?

No output schema exists, so the description carries the return-shape burden and does so partially by naming location, status and impacts. Combined with full schema coverage and annotations, it is nearly complete for a filtered-search tool; only deeper result-shape detail is absent.

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 the schema already documents all seven filters. The description's mention of event types and location/status/impacts loosely maps to the evento, canton/provincia and estado filters but adds no syntax or format 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 (search) and resource (SGR/COE risk events) and enumerates the content returned: landslides, floods, structural damage with location, status and impacts. It explicitly distinguishes itself from the sibling search_sgr_sitreps by declaring 'No history'.

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?

Gives the when ('current and recent ... from the live COE feed') and the when-not plus alternative ('No history; for past event dossiers use search_sgr_sitreps'). The routing decision is fully specified without inference.

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