Skip to main content
Glama

Active Storms

active_storms
Read-onlyIdempotent

List currently active tropical cyclones (tropical storms / hurricanes) from the US National Hurricane Center, name, classification, Saffir-Simpson category, position, max winds, pressure, movement, and links to official advisories/forecast cone. Filter by basin. Keyless. Returns an empty list in the off-season.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
basinNoOptional filter: "atlantic", "eastern-pacific", or "central-pacific".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "basin": "atlantic"
      +  },
      +  {
      +    "basin": "eastern-pacific"
      +  }
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds behavior the annotations do not: keyless access, the upstream data source (US NHC), and the off-season empty-list semantics, which is exactly the failure mode an agent would otherwise misread.

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?

Packed but front-loaded: purpose first, then returned fields, then filter, then operational caveats. The first sentence is long and comma-spliced, which slightly hurts scanability, but no sentence is filler.

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 one-parameter read tool with no output schema, the description supplies the source, the full field list, the filter behavior, auth expectations, and the empty-result case. An agent has everything needed to call it and interpret its output correctly.

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 the single `basin` parameter is fully documented in-schema with its three allowed values. The description only restates "Filter by basin" without adding format, default, or behavior for an unrecognized basin value, so 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?

Specific verb plus resource: "List currently active tropical cyclones (tropical storms / hurricanes) from the US National Hurricane Center," and it enumerates the returned fields (classification, category, position, winds, pressure, movement, advisory links). No sibling in the catalog overlaps with this domain, so the tool is unambiguous on its own.

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 operating context: "Keyless" (no auth needed), "Filter by basin" as the only narrowing option, and "Returns an empty list in the off-season" so an agent knows an empty result is expected rather than an error. No explicit when-not guidance or alternative named, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.