Criora: climate & disaster risk for any place

Official warnings in the map's view

get_map_warnings

Read-onlyIdempotent

The official warnings the interactive map draws over a view: each hazard's edge at each class and its symbols, at the view's zoom. The map calls it in clients that display it; to list the warnings near a place, use get_hazards_near.

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": {
      "west": "<west>",
      "south": "<south>",
      "east": "<east>",
      "north": "<north>",
      "zoom": "<zoom>"
    },
    "name": "get_map_warnings"
  }
}

Input Schema

Name	Required	Description
`east`	Yes	The view's east edge, unwrapped past 180
`west`	Yes	The view's west edge, unwrapped past 180
`zoom`	Yes	The zoom the view is drawn at
`north`	Yes	The view's north edge
`south`	Yes	The view's south edge

Output Schema

Name	Required	Description	Default
`zoom`	Yes
`edges`	Yes
`tracks`	Yes
`symbols`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 5, 2026
- removedOutput schema / $defs / MapWarningEdge / properties / events / description
```
Removed value: -"Every warning inside, most serious first"
```
- removedOutput schema / $defs / MapWarningEdge / properties / rank / description
```
Removed value: -"0 (low) to 3 (critical)"
```
- removedOutput schema / $defs / MapWarningEdge / properties / rings / description
```
Removed value: -"Each ring as its first point and then the steps to the next, in whole Web Mercator pixels"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / events / description
```
Removed value: -"Every warning it stands for, most serious first"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / rank / description
```
Removed value: -"0 (low) to 3 (critical)"
```
- removedOutput schema / $defs / MapWarningTrack / properties / events / description
```
Removed value: -"The storm"
```
- removedOutput schema / $defs / MapWarningTrack / properties / forecast / description
```
Removed value: -"Where it is forecast to go, from its last observed point; else where it has been"
```
- removedOutput schema / $defs / MapWarningTrack / properties / line / description
```
Removed value: -"Its first point and then the steps to the next, in whole Web Mercator pixels"
```
- removedOutput schema / $defs / MapWarningTrack / properties / rank / description
```
Removed value: -"0 (low) to 3 (critical)"
```
- removedOutput schema / properties / zoom / description
```
Removed value: -"The zoom the pixels are counted at: the world is 512 times 2 to it across"
```
Changed31 schema fields changedNov 2, 2026
- removedInput schema / properties / east / title
```
Removed value: -"East"
```
- removedInput schema / properties / north / title
```
Removed value: -"North"
```
- removedInput schema / properties / south / title
```
Removed value: -"South"
```
- removedInput schema / properties / west / title
```
Removed value: -"West"
```
- removedInput schema / properties / zoom / title
```
Removed value: -"Zoom"
```
- removedInput schema / title
```
Removed value: -"get_map_warningsArguments"
```
- removedOutput schema / $defs / MapWarningEdge / properties / events / title
```
Removed value: -"Events"
```
- removedOutput schema / $defs / MapWarningEdge / properties / rank / title
```
Removed value: -"Rank"
```
- removedOutput schema / $defs / MapWarningEdge / properties / rings / title
```
Removed value: -"Rings"
```
- removedOutput schema / $defs / MapWarningEdge / properties / severity / title
```
Removed value: -"Severity"
```
- removedOutput schema / $defs / MapWarningEdge / properties / type / title
```
Removed value: -"Type"
```
- removedOutput schema / $defs / MapWarningEdge / title
```
Removed value: -"MapWarningEdge"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / events / title
```
Removed value: -"Events"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / rank / title
```
Removed value: -"Rank"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / severity / title
```
Removed value: -"Severity"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / type / title
```
Removed value: -"Type"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / x / title
```
Removed value: -"X"
```
- removedOutput schema / $defs / MapWarningSymbol / properties / y / title
```
Removed value: -"Y"
```
- removedOutput schema / $defs / MapWarningSymbol / title
```
Removed value: -"MapWarningSymbol"
```
- removedOutput schema / $defs / MapWarningTrack / properties / events / title
```
Removed value: -"Events"
```
- removedOutput schema / $defs / MapWarningTrack / properties / forecast / title
```
Removed value: -"Forecast"
```
- removedOutput schema / $defs / MapWarningTrack / properties / line / title
```
Removed value: -"Line"
```
- removedOutput schema / $defs / MapWarningTrack / properties / rank / title
```
Removed value: -"Rank"
```
- removedOutput schema / $defs / MapWarningTrack / properties / severity / title
```
Removed value: -"Severity"
```
- removedOutput schema / $defs / MapWarningTrack / properties / type / title
```
Removed value: -"Type"
```
- removedOutput schema / $defs / MapWarningTrack / title
```
Removed value: -"MapWarningTrack"
```
- removedOutput schema / properties / edges / title
```
Removed value: -"Edges"
```
- removedOutput schema / properties / symbols / title
```
Removed value: -"Symbols"
```
- removedOutput schema / properties / tracks / title
```
Removed value: -"Tracks"
```
- removedOutput schema / properties / zoom / title
```
Removed value: -"Zoom"
```
- removedOutput schema / title
```
Removed value: -"MapWarnings"
```
AddedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. Beyond that, the description discloses that output is zoom-dependent rendering geometry (edges at each class plus symbols), which is genuinely useful behavioral context. It says nothing about response size or cost at low zoom, which is the main remaining gap.

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?

Two compact sentences: the resource description comes first, then the routing advice, which is the right order. The phrase 'at the view's zoom' partially repeats the earlier 'over a view', but there is no padding beyond that.

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 a full input schema, an output schema, and rich annotations, the description only needs to frame purpose and routing. It does that, and it explains the rendering semantics (edges per class, symbols). Undefined domain terms such as 'class' and the absence of output-volume warnings are minor omissions for a read-only tool.

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 description coverage is 100%, so all five bounding-box and zoom parameters are already documented, including the unwrapped-longitude subtlety. The description reinforces that zoom drives output granularity ('each hazard's edge at each class') but adds no format or range guidance beyond the schema. Baseline 3 applies when the schema carries the parameter detail.

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 (official warnings drawn over a map view, with each hazard's edge per class plus symbols) and ties the output to the zoom. An agent can distinguish it from get_hazards_near based on the text. It lacks an explicit retrieval verb, but the noun phrase plus the rendering detail makes the purpose unambiguous.

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 states the context in which the tool is intended ('the map calls it in clients that display it') and names an alternative with the condition that selects it ('to list the warnings near a place, use get_hazards_near'). It does not mention other warning-listing siblings such as list_hazards, so a small routing gap remains.

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

All Criora: climate & disaster risk for any place 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.