Skip to main content
Glama

Travel Advisories

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Advisories

advisories
Read-onlyIdempotent

List current US State Department travel advisories. Filter by country keyword and/or minimum threat level (1=normal precautions, 2=increased caution, 3=reconsider travel, 4=do not travel). Sorted by threat level (highest first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoExact threat level to filter (1-4).
limitNoMax advisories to return (1-250, default 50).
queryNoCountry name filter, e.g. "mexico", "france".
min_levelNoMinimum threat level (e.g. 3 → only "reconsider travel" and "do not travel").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "mexico"
+  },
+  {
+    "limit": 20,
+    "min_level": 3
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds that results are sorted by threat level (highest first), which is not in annotations. No contradictions.

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, front-loaded with the main action, no wasted words. Each sentence adds value: purpose first, then filtering and sorting.

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?

Given no output schema, the description covers purpose, filtering, and sorting adequately. It could mention that the sibling 'advisory' tool is for single-country details, but this is a minor gap.

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 100% with descriptions for all parameters. The description adds context by explaining the threat level mapping (1-4) and the sorting order, which goes beyond the schema's descriptions.

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 clearly states the tool lists current US State Department travel advisories, with a specific verb ('list'), resource ('travel advisories'), and source ('US State Department'). It is distinct from siblings like 'advisory' which likely returns a single advisory.

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?

The description explains how to filter by country keyword and minimum threat level, and mentions sorting. However, it does not explicitly say when to use this tool versus the sibling 'advisory' tool for detailed single-country info.

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

All Travel Advisories toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources