Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Listar estaciones del SAT de tsunami

list_sat_tsunami
Read-only

List SGR tsunami early-warning (SAT) stations with codes and coordinates for Ecuador; this returns a static station inventory, not live alerts.

Instructions

SGR tsunami early-warning (SAT) stations with codes and coordinates: a static station list, not alerts. For recent seismic events use search_sismos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax stations to include in the response (default 30)
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 / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max stations to include in the response (default 30)"
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"list_sat_tsunamiArguments"
    • removedOutput schema / title
      Removed value: -"list_sat_tsunamiDictOutput"
  4. First observedv0.8.12

TDQS

A4.5/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 meaningful behavioral context beyond that: it is a static list, not an alert feed, and it returns codes and coordinates. It does not cover pagination or rate limits, but the added distinction is valuable.

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 with zero waste. The core purpose and scope are front-loaded, and the sibling alternative follows naturally.

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

Completeness5/5

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

For a simple static list with a fully documented two-parameter schema and no output schema, the description is complete enough: it states what the tool returns (codes and coordinates), what it is not (alerts), and when to use a sibling instead.

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 both parameters (limit, format) have complete descriptions, so the schema already carries parameter meaning. The description does not add syntax or format details for limit or format, making the baseline 3 appropriate.

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 states a specific resource (SGR tsunami early-warning SAT stations), its key output fields (codes and coordinates), and explicitly distinguishes itself from alerts. The sibling differentiation is clear: 'For recent seismic events use search_sismos.'

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?

It provides explicit when-not guidance ('not alerts') and names the alternative for a different need ('For recent seismic events use search_sismos'). The scope of this tool, a static station list, is stated directly.

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