Skip to main content
Glama

Smarter Weather

by io.github.smarterweather

Get platform status

get_platform_status
Read-onlyIdempotent

Current data-freshness status of the weather platform: overall state, per-source states (ok / degraded / outage / no_signal), open incidents with cause attribution (provider outage vs internal processing delay), and active provider advisories. Use this when a user asks whether data is current, when other tools return surprisingly stale data, or before presenting time-critical weather. If a source is degraded or in outage, tell the user their data may be stale rather than presenting it as live. No inputs. Refreshed about every 5 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_okNotrue: list every monitored source including healthy ones. false (default): only sources that are not ok, keeping the response compact.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
overallYesWorst state across customer-facing data sources; "unknown" when status is unavailable.
sourcesNo
advisoriesNo
generated_atNoWhen the status document was generated (UTC).

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedOutput schema / properties / advisories / items / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / properties / sources / items / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / properties / sources / items / properties / incident / additionalProperties
      Previous value: -falseNew value: +true
  2. Changed1 schema field changed
    • changedOutput schema / properties / sources / items / properties / incident / properties / since / type
      Previous value: -"string"New value: +[
+  "string",
+  "number"
+]
  3. Changed1 schema field changed
    • addedOutput schema / properties / sources / items / properties / warming
      Added value: +{
+  "description": "true when no_signal only means monitoring is still warming up (not an outage).",
+  "type": "boolean"
+}
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond that: the status refreshes every ~5 minutes, incidents are categorized by cause, and the agent should warn users about potentially stale data. The phrase 'No inputs' is slightly misleading given the optional include_ok parameter, but this is more of a parameter-semantics issue than a behavioral one.

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 well-structured: it front-loads the purpose, then gives usage guidance and an important staleness caveat, and ends with refresh cadence. The 'No inputs' sentence is inaccurate and unnecessary, but the rest is tight and efficient.

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 an output schema present and annotations covering safety, the description does not need to explain return values in depth. It covers when to use the tool, what the status categories mean, and how to handle degraded/outage states. The only notable gap is the misleading 'No inputs' statement, which is offset by the fully described input schema.

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?

The input schema fully documents include_ok with a clear description and default, so schema coverage is 100%. The description's 'No inputs' line is imprecise because the tool does accept an optional boolean, though it may be intended to mean 'no required inputs.' Overall, the description adds no real parameter meaning beyond the schema.

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 clearly states it returns 'current data-freshness status of the weather platform' and lists the specific contents: overall state, per-source states, open incidents, and provider advisories. This distinguishes it from sibling tools like get_current_conditions or get_observations, which return weather data rather than platform freshness.

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?

It gives explicit use cases: when a user asks whether data is current, when other tools return surprisingly stale data, or before presenting time-critical weather. It does not name alternatives or state when not to use the tool, 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.

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