Skip to main content
Glama

Smarter Weather

by io.github.smarterweather

Get forecast discussion

get_forecast_discussion
Read-onlyIdempotent

Expert forecaster text products. type=afd: Area Forecast Discussion. type=hwo: Hazardous Weather Outlook. type=now: WFO short-term NOW. type=fwf/hls/esf: local fire weather / hurricane local statement / hydrologic discussion. type=mcd: SPC Mesoscale Discussion. type=mpd: WPC Mesoscale Precipitation Discussion (flash flood). type=swo/fwd/ero: national outlook discussions. type=tcd/tcp/tcm/twd/two: NHC tropical text (type=two is the text TWO, not GIS nhc_two). type=pmd: WPC/CPC desk discussion (pass awips_id for a specific desk, e.g. PMDSPD). type=pwo: SPC public weather outlook. National types (swo/fwd/ero/tcd/tcp/tcm/twd/two/pmd/pwo) need no location; day selects the outlook day for swo and fwd. summary_only=true returns the pipeline LLM summary without the full body. Examples: {"location": "Des Moines", "type": "afd"} or {"type": "swo", "day": 2, "summary_only": true}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoOutlook day for type=swo or type=fwd (1-8). Ignored for the other types; WPC files ERO days 1-3 under one product.
latNoLatitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
lonNoLongitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
wfoNoWFO identifier override (e.g. BOU). Default: resolved from the location.
typeYesProduct type: afd (WFO discussion), hwo (hazard outlook), now (short-term NOW), fwf/hls/esf (local WFO), mcd (SPC mesoscale), mpd (WPC precipitation discussion), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall), tcd/tcp/tcm/twd/two (NHC tropical text; two is text TWO not GIS), pmd (desk discussion), pwo (SPC public outlook).
limitNoNumber of recent products (1-10). Default 1 (latest).
awips_idNoFull AWIPS identifier (e.g. TCDAT1, PMDSPD). More specific than type + location. Exact source_ref match.
locationNoFree-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
summary_onlyNoReturn only the LLM summary + sections, omitting the full body text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
locationNo
productsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / awips_id
      Added value: +{
+  "description": "Full AWIPS identifier (e.g. TCDAT1, PMDSPD). More specific than type + location. Exact source_ref match.",
+  "maxLength": 12,
+  "minLength": 3,
+  "type": "string"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Product type: afd (WFO discussion), hwo (hazard outlook), mcd (SPC mesoscale), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall)."New value: +"Product type: afd (WFO discussion), hwo (hazard outlook), now (short-term NOW), fwf/hls/esf (local WFO), mcd (SPC mesoscale), mpd (WPC precipitation discussion), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall), tcd/tcp/tcm/twd/two (NHC tropical text; two is text TWO not GIS), pmd (desk discussion), pwo (SPC public outlook)."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "afd",
-  "hwo",
-  "mcd",
-  "swo",
-  "fwd",
-  "ero"
-]New value: +[
+  "afd",
+  "hwo",
+  "now",
+  "fwf",
+  "hls",
+  "esf",
+  "mcd",
+  "mpd",
+  "swo",
+  "fwd",
+  "ero",
+  "tcd",
+  "tcp",
+  "tcm",
+  "twd",
+  "two",
+  "pmd",
+  "pwo"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / day
      Added value: +{
+  "default": 1,
+  "description": "Outlook day for type=swo or type=fwd (1-8). Ignored for the other types; WPC files ERO days 1-3 under one product.",
+  "maximum": 8,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Product type: afd (WFO discussion), hwo (hazard outlook), mcd (SPC mesoscale)."New value: +"Product type: afd (WFO discussion), hwo (hazard outlook), mcd (SPC mesoscale), swo (SPC convective outlook), fwd (SPC fire weather), ero (WPC excessive rainfall)."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "afd",
-  "hwo",
-  "mcd"
-]New value: +[
+  "afd",
+  "hwo",
+  "mcd",
+  "swo",
+  "fwd",
+  "ero"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses several non-obvious behaviors: type=two is the text TWO not the GIS product, pmd requires an awips_id for a specific desk, WPC files ERO days 1-3 under one product, summary_only returns the pipeline LLM summary, and national types accept no location. These details go well beyond the annotations (readOnly, idempotent, non-destructive) and materially improve correct invocation.

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?

The description is long but necessarily so, since it must document 18 product type codes. It is front-loaded with the core purpose and uses a compact semicolon-separated style with concrete examples at the end. A small deduction for redundancy: much of the type-by-type explanation is duplicated in the input schema's enum descriptions.

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?

Given 9 parameters, 1 required, a rich enum, and an output schema, the description covers all critical invocation aspects: type selection, location options, day semantics, summary_only, and representative examples. The presence of an output schema means the response format need not be described. No notable gaps remain.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by giving concrete invocation examples, clarifying that national types require no location, and explaining the pmd desk-desk behavior with a sample awips_id. It partially repeats schema descriptions for the type enum, which keeps it from a 5.

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 opens with 'Expert forecaster text products' and enumerates every product type with a one-line explanation, making it clear this tool retrieves NWS/SPC/WPC/NHC text forecast discussions, not gridded forecast data. The name and title align with the described content, and the level of detail distinguishes it from sibling tools like get_forecast and get_current_conditions.

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 description provides clear context for when to use the tool and how to select among its many type values, including the rule that national types need no location and that `day` only applies to swo/fwd. It does not explicitly name sibling alternatives or state when not to use it, but the context is concrete enough that an agent can infer appropriate usage.

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

All Smarter Weather toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, and the detailed descriptions generally prevent misselection. A few near-overlapping pairs exist — get_current_conditions vs get_observations, and get_forecast already bundling current conditions, alerts, and outlooks — so some ambiguity remains.

Naming Consistency4/5

The overwhelming majority of tools follow a get_<object>_<modifier> pattern in snake_case, and the non-get tools still use an imperative verb_noun form. The mix of verbs (get, list, describe, find, query, search, reverse) is a minor inconsistency, but the overall pattern is predictable.

Tool Count2/5

At 32 tools, the surface is heavy and exceeds the 25+ threshold for a large tool set. The weather domain justifies much of the breadth, but several tools overlap in scope and could plausibly be consolidated, making the count feel higher than necessary.

Completeness5/5

The tool set comprehensively covers current conditions, forecasts, hourly data, climate, alerts, severe weather, air quality, tropical systems, upper-air soundings, maps, model data, geocoding, and platform status. There are no obvious dead-end workflows, and raw access via query_dataset fills most remaining gaps.

Resources