Smarter Weather

Get status

get_status

Read-onlyIdempotent

Data freshness of the weather platform (no inputs needed; refreshed about every 5 minutes): overall state, per-source states (ok / degraded / outage / no_signal), open incidents with their cause (provider outage vs internal processing delay) and active provider advisories. Use it when asked whether data is current, or when other tools return stale-looking data. If a source is degraded or in outage, say the data may be stale rather than presenting it as live. Example: {}.

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

Input Schema

Name	Required	Description	Default
`include_ok`	No	true: every monitored source, healthy ones too. false (default): only sources that are not ok.

Output Schema

Name	Required	Description
`note`	No
`overall`	Yes	Worst state across customer-facing data sources; "unknown" when status is unavailable.
`sources`	No
`advisories`	No
`generated_at`	No	When the status document was generated (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / include_ok / description

Previous value: -"true: list every monitored source including healthy ones. false (default): only sources that are not ok, keeping the response compact."New value: +"true: every monitored source, healthy ones too. false (default): only sources that are not ok."

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds valuable context beyond those annotations: refresh cadence, source-state categories, incident cause distinction, and advisory inclusion. It does not cover rate limits or auth, but that is minor for this status tool.

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 compact and front-loads the purpose, usage guidance, and interpretation rule. The parenthetical listing of states and incident causes is dense but useful, and the example is appropriate for a zero-required-parameter call.

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?

An output schema exists, so the description need not document return structure. Given the annotations and output schema, the description supplies enough context to call and interpret this status tool 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%, so the include_ok parameter is already fully documented. The description says no inputs are needed and provides an empty example, which is accurate for required parameters but does not add meaning beyond the schema for the optional include_ok flag.

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 states a specific resource and scope: data freshness of the weather platform, including overall state, per-source states, open incidents, and active provider advisories. It is clearly distinguishable from sibling tools such as get_current_conditions or get_alerts.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: when asked whether data is current, or when other tools return stale-looking data. It also gives clear interpretation guidance for degraded or outage states.

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

All Smarter Weather tools Inspect

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.