Skip to main content
Glama

Current official emergency alerts

get_emergency_alerts
Read-only

Retrieve active Alertswiss population warnings for Switzerland, including event type, severity, affected regions and official instructions; filter by region or canton when needed.

Instructions

All currently active Alertswiss population warnings for Switzerland: event type, severity, affected regions, official instructions. Optionally filter by a region or canton (code or name in any national language or English, accents optional).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
regionNoFilter by region/canton, e.g. 'Zürich', 'Zurich', 'ZH', 'Ticino', 'Genève'
include_testsNoInclude technical test alerts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real value on top by defining the temporal window ('currently active') and the returned content categories. It stops short of stating refresh cadence, the issuing authority relationship, or that include_tests excludes test alerts by default, which matters for an emergency feed.

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

Conciseness5/5

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

Two sentences, both front-loaded: the resource and scope come first, the optional filter second. No filler or restatement of the title.

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 three-parameter read-only tool with no output schema, this is nearly sufficient: the agent knows what it gets and how to filter. The one tension is that the description says 'All' active warnings while limit caps results at 20 by default, a truncation behavior the description never acknowledges.

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 67%, and the description compensates for the weakest documented parameter: it explains that region accepts a code or a name in any national language or English with optional accents, which goes beyond the schema's four examples. It adds nothing about limit's pagination semantics, leaving a small gap.

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?

Names a specific resource and scope: 'All currently active Alertswiss population warnings for Switzerland', and enumerates the payload fields (event type, severity, affected regions, official instructions). This distinguishes it cleanly from siblings like get_avalanche_bulletin or get_earthquake_details, which cover single hazard domains.

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

Usage Guidelines3/5

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

The phrase 'currently active' establishes when the tool applies (live warnings, not historical), and the region filter is framed as optional, which implicitly tells the agent the unfiltered call is valid. However, there is no explicit when-not guidance and no named alternative for historical or hazard-specific queries.

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

Deploy Server

Other Tools