Smarter Weather

Describe data

describe_data

Read-onlyIdempotent

A dataset's variables or properties (standard names, units, categories, bands, aggregates), horizon, step, cadence, freshness, cost class, verified examples and an example_query to read its values; a map layer's axes (source, region, facts) and render (visual) call. Free. Call it when a grid or snapshot hit's call lacks the variable you need (with no variable, it may read only the headline one), or to check units, horizon or cost; not needed when the hit's call already names what you need: run that. Example: {"dataset_id": ""}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataset_id": "<dataset_id>"
    },
    "name": "describe_data"
  }
}

Input Schema

Name	Required	Description	Default
`dataset_id`	Yes	A dataset id from search_data or get_data (1-80 chars).

Output Schema

Name	Required	Description
`map`	No	A map layer: its axes, sibling sectors, `select` (its id and its <family>:<pick>), the render (visual) call, and a note.
`detail`	Yes
`dataset_id`	Yes
`attribution`	No	Attribution the dataset licence requires. Cite it when quoting these values.
`data_status`	No	Present only when the data service could not answer: a cached copy, or catalog facts without freshness.
`example_query`	No	get_data arguments for this dataset; add a location.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / dataset_id / description

Previous value: -"A dataset id from search_data or get_data (1-80 characters)."New value: +"A dataset id from search_data or get_data (1-80 chars)."

Changed1 schema field changedNov 6, 2026

changedOutput schema / properties / map / description

Previous value: -"A map layer: its axes, sibling sectors, the render (visual) call that draws it, and a note."New value: +"A map layer: its axes, sibling sectors, `select` (its id and its <family>:<pick>), the render (visual) call, and a note."

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / map

Added value: +{
+  "additionalProperties": {},
+  "description": "A map layer: its axes, sibling sectors, the render (visual) call that draws it, and a note.",
+  "properties": {},
+  "type": "object"
+}

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

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / dataset_id / description

Previous value: -"Pipeline dataset identifier (e.g. \"nbm_conus\", \"mrms_reflectivity_conus\"). Discover valid values with search_data; inspect variables with describe_data. Length: 1-80 characters."New value: +"A dataset id from search_data or get_data (1-80 characters)."

Changed1 schema field changedOct 30, 2026

changedOutput schema / properties / example_query / description

Previous value: -"query_dataset arguments for this dataset; add a location."New value: +"get_data arguments for this dataset; add a location."

AddedOct 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the bar is lower, yet the description still adds real context: it is free, it exposes an example_query usable to read values, and a call without `variable` may return only the headline variable. It does not discuss pagination or rate limiting, but for a metadata lookup that is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a dense run-on packing many returned fields into nested parentheticals, which is hard to parse and partly redundant with the output schema. The when-to-use sentence and the concrete example are well placed and earn their space.

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?

For a one-parameter, read-only lookup with an output schema, this is effectively complete: it explains what is returned in prose, when to reach for it versus just running the hit's `call`, that it is free, and gives a JSON example with dataset_id sourced from search_data. Slight redundancy with the output schema is the only cost.

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% on the single `dataset_id` parameter, and the schema already says it comes from search_data or get_data, so the description adds little. The talk of a `variable` argument is not a parameter of this tool and could momentarily confuse an agent reading the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely (dataset variables/properties, horizon, step, cadence, cost class, examples, example_query; and map-layer axes plus render call), which clearly separates it from search_data and get_data. It lacks a leading verb such as 'Describe', so the opening reads as a noun list rather than an action, but the intent is unambiguous by the second sentence.

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 states both sides of the decision explicitly: call it when a grid or snapshot hit's `call` lacks the needed variable, or to check units/horizon/cost; do not call it when the hit's `call` already names what you need — run that instead. It even notes the edge case that without `variable` only the headline one may be readable.

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.