Skip to main content
Glama
Sign In

Gillby

by io.github.OneWave-AI
OverviewDiscussionsAdmin

Active hurricanes and tropical cyclones

get_hurricanes
Read-onlyIdempotent

Active NHC tropical cyclones in the Atlantic and eastern/central Pacific. Returns position, maximum sustained wind (kt), pressure (mb), movement (degrees toward and kt), advisory timestamps and official advisory/forecast/cone links. Preserve stale/unavailable status. An empty active-storm list does not rule out developing systems or local hazards. The cone is not an impact boundary. Follow official local warnings.

Units: sustained wind and movement speed kt; pressure mb; coordinates degrees; movement bearings TOWARD. Advisory and retrieval timestamps are separate. Returns data and source/freshness metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hurricanes"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive semantics, so the description's added value is real: it discloses 'Preserve stale/unavailable status', that advisory and retrieval timestamps are distinct, and that source/freshness metadata is returned. It stops short of auth, rate limits, or pagination details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded: identity and returned fields first, then interpretive cautions, then units and timestamp semantics. It is dense and multi-sentence, but each block (units, staleness, cone caveat) carries information an agent needs; little is wasted.

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?

With no output schema, the description carries the return-value burden and does so well (fields, units, freshness metadata). The remaining gap is the basin parameter's enum values, which are neither described in the schema nor fully explained in the description.

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 0%, so the description must compensate. It names the geographic basins covered ('Atlantic and eastern/central Pacific'), which partially decodes the al/ep/cp enum values, but it never explains the 'all' default or maps abbreviations to values, leaving the basin parameter under-documented.

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?

The description gives a specific verb+resource ('Active NHC tropical cyclones in the Atlantic and eastern/central Pacific') and enumerates the returned fields (position, wind, pressure, movement, advisory timestamps, links). The word 'Active' implicitly separates it from get_hurricane_history, but no sibling is named explicitly, so it falls short of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: it is clearly a situational-awareness feed for current storms, and the caveat that an empty list doesn't rule out developing systems hints at when not to rely on it. There is no explicit routing guidance against siblings like get_hurricane_history or get_marine_alerts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gillby toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources