Skip to main content
Glama

Atlantic tropical outlook

get_tropical_outlook
Read-onlyIdempotent

Atlantic-basin tropical activity from the NOAA National Hurricane Center: named storms, and the unnamed areas NHC is watching for development, with formation chances. Not specific to Crosby, TX. Refreshed about hourly June–November and about daily the rest of the year. Returns an explicit all-clear only when both lists are empty; an empty storms list alone does not mean a quiet basin.

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_tropical_outlook"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
basinYes
sourceNo
stormsYesNamed/numbered cyclones only. Empty is common and does not by itself mean nothing is brewing; unnamed areas are in `disturbances`.
updatedNoISO 8601 timestamp of the last data refresh.
disturbancesNoAreas the NHC is watching for development but has NOT named — the shaded areas on its graphical outlook. `null` means the outlook could not be read (status unknown); `[]` means the NHC is watching nothing — two different states. A formation chance is neither a storm nor a forecast track.
outlookIssuedNoISO 8601 timestamp of the last data refresh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedOutput schema / properties / disturbances / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "properties": {
      +        "area": {
      +          "description": "NHC's own name for the area, in official English.",
      +          "type": "string"
      +        },
      +        "chance48Category": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "low / medium / high, NHC's own wording."
      +        },
      +        "chance48Percent": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "chance7DayCategory": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "chance7DayPercent": {
      +          "anyOf": [
      +            {
      +              "type": "integer"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "id": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "description": "Invest number when assigned, e.g. \"AL95\"."
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / disturbances / description
      Previous value: -"Areas the NHC is watching for development but has NOT named — the shaded areas on its graphical outlook. `null` means the outlook could not be read; `[]` means the NHC is watching nothing. Do not conflate the two, and do not report a formation chance as a storm or as a forecast track."New value: +"Areas the NHC is watching for development but has NOT named — the shaded areas on its graphical outlook. `null` means the outlook could not be read (status unknown); `[]` means the NHC is watching nothing — two different states. A formation chance is neither a storm nor a forecast track."
    • removedOutput schema / properties / disturbances / items
      Removed value: -{
      -  "properties": {
      -    "area": {
      -      "description": "NHC's own name for the area, in official English.",
      -      "type": "string"
      -    },
      -    "chance48Category": {
      -      "description": "low / medium / high, NHC's own wording.",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "chance48Percent": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "chance7DayCategory": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "chance7DayPercent": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "id": {
      -      "description": "Invest number when assigned, e.g. \"AL95\".",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}
    • removedOutput schema / properties / disturbances / type
      Removed value: -[
      -  "array",
      -  "null"
      -]
    • addedOutput schema / properties / outlookIssued / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / outlookIssued / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • changedOutput schema / properties / storms / description
      Previous value: -"Named/numbered cyclones only. Empty is common and does NOT imply nothing is brewing — check `disturbances` too."New value: +"Named/numbered cyclones only. Empty is common and does not by itself mean nothing is brewing; unnamed areas are in `disturbances`."
    • addedOutput schema / properties / storms / items / properties / lat / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / storms / items / properties / lat / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / storms / items / properties / lon / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / storms / items / properties / lon / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / storms / items / properties / movementDirection / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / storms / items / properties / movementDirection / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / storms / items / properties / pressureMb / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / storms / items / properties / pressureMb / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / storms / items / properties / windMph / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / storms / items / properties / windMph / type
      Removed value: -[
      -  "integer",
      -  "null"
      -]
    • addedOutput schema / properties / updated / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / updated / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / disturbances
      Added value: +{
      +  "description": "Areas the NHC is watching for development but has NOT named — the shaded areas on its graphical outlook. `null` means the outlook could not be read; `[]` means the NHC is watching nothing. Do not conflate the two, and do not report a formation chance as a storm or as a forecast track.",
      +  "items": {
      +    "properties": {
      +      "area": {
      +        "description": "NHC's own name for the area, in official English.",
      +        "type": "string"
      +      },
      +      "chance48Category": {
      +        "description": "low / medium / high, NHC's own wording.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "chance48Percent": {
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "chance7DayCategory": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "chance7DayPercent": {
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "id": {
      +        "description": "Invest number when assigned, e.g. \"AL95\".",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / outlookIssued
      Added value: +{
      +  "description": "ISO 8601 timestamp of the last data refresh.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / storms / description
      Previous value: -"Empty when the basin is quiet — the normal state most of the year."New value: +"Named/numbered cyclones only. Empty is common and does NOT imply nothing is brewing — check `disturbances` too."
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description appropriately spends its words elsewhere: data currency and cadence. The all-clear caveat — that an empty `storms` list alone does not mean a quiet basin — is a genuinely non-obvious interpretation rule that the schema and annotations cannot convey.

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?

Three tight sentences, front-loaded with the resource and scope, then the caveat. The mid-sentence "Not specific to Crosby, TX" interjection reads slightly awkwardly where it sits, but every sentence 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?

An output schema exists, so return values need no prose explanation, and the description adds what the schema cannot: refresh cadence and the empty-list interpretation rule. It stops short of stating whether other basins (e.g., East Pacific) are covered or how formation-chance percentages should be read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters and schema coverage is 100%, so there is nothing for the description to clarify; the 4 baseline for a zero-parameter tool applies. No fabricated parameter talk is introduced.

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 concrete verb-and-resource pair: Atlantic-basin tropical activity sourced from the NOAA National Hurricane Center, enumerating exactly what is returned (named storms, watched unnamed areas, formation chances). The clause "Not specific to Crosby, TX" separates it from the local-condition siblings without needing to read their schemas.

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?

The "Not specific to Crosby, TX" note functions as an explicit when-not: use this for basin-wide tropical threat, not for local Crosby observations. The refresh cadence (hourly June–November, daily otherwise) further implies when a call is worth repeating, but no alternative tool is named for the local case, leaving the routing implicit.

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.