Skip to main content
Glama

get_safety_alerts

Read-onlyIdempotent

Get active safety alerts from SafeTravel.is for a location.

Provide either operator_id OR latitude+longitude.
Response includes `location` with name, latitude, longitude for map context.

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

Input Schema

NameRequiredDescriptionDefault
latitudeNoWGS84 latitude. Required if operator_id is not provided.
longitudeNoWGS84 longitude. Required if operator_id is not provided.
operator_idNoOperator slug to resolve location automatically. Use this OR latitude+longitude, not both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful behavior context: results are limited to *active* alerts and the response carries a `location` object for map placement. It does not say what happens when neither location form is supplied, which matters because the schema marks all three parameters optional.

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?

Three short lines, front-loaded with the verb and resource, then the invocation constraint, then the one return-shape detail worth surfacing. Nothing is padded or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 single sentence about the `location` field is sufficient and return values need no further explanation. The remaining gap is the all-optional parameter set: the description says 'provide either' but never states the fallback or error when neither operator_id nor coordinates are given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines each field and the either/or rule, and the description reinforces the mutually exclusive location forms in the calling sequence rather than contradicting or duplicating at length. Combined with the schema text, an agent has everything needed to build a valid call.

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?

States a specific verb and resource ('Get active safety alerts') plus the upstream source (SafeTravel.is) and the scoping unit (a location). An agent can tell this is a read of external hazard data rather than weather, road, or avalanche conditions, though it never names a sibling to contrast against.

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 line 'Provide either operator_id OR latitude+longitude' gives invocation guidance but is purely parameter routing, which the schema already states. There is no when-to-use framing (e.g. before booking travel in an area) and no when-not guidance relative to the other hazard/condition tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources