Skip to main content
Glama

Buscar eventos de riesgo del SGR

search_eventos_riesgo
Read-only

Search live SGR risk events in Ecuador, such as landslides, floods, and structural damage, with location, status, and impacts. Filter by province, canton, event type, or status.

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")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)"
  2. 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"
  3. 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 declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the data comes from a live feed and is recency-limited, with no historical coverage. It omits freshness latency, pagination, and any rate/auth constraints, 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 dense sentences, zero padding, with the scope definition and content examples front-loaded before the sibling redirect. Every clause carries information an agent needs.

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 filtered search tool with a full output schema and annotations covering the safety profile, the description supplies scope, content types, and the key exclusion. Remaining gaps (freshness window semantics, result volume/pagination behavior) are minor and partly covered by the limit parameter.

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 all seven parameters are already documented with examples and defaults. The description's mention of event types and location/status fields loosely maps to the evento, canton/provincia, and estado filters but adds no syntax or format detail 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?

States a specific verb and resource (search SGR risk events), narrows scope to "current and recent" from the "live COE feed," and enumerates content types (landslides, floods, structural damage) plus returned fields (location, status, impacts). It also names the sibling it is not, so an agent can distinguish it from search_sgr_sitreps without opening either schema.

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?

Explicitly delimits when not to use it ("No history") and routes to the correct alternative ("for past event dossiers use search_sgr_sitreps"). Both the selection condition and the alternative are stated, leaving nothing to 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