Skip to main content
Glama

get_travel_rule

Read-onlyIdempotent

Retrieve dated, evidence-qualified travel rule information for a passport and destination, including conditions, coverage gaps, and warnings, without inferring eligibility from missing context.

Instructions

Read-only get travel rule. Preserve evidence dates, conditions, coverage gaps and warnings. Missing context never establishes eligibility or a travel waiver.

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": {
      "passport": "<passport>",
      "destination": "<destination>"
    },
    "name": "get_travel_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNo
purposeNo
releaseNo
passportYes
transportNo
destinationYes
documentTypeNo
qualifyingVisaNo

Output Schema

NameRequiredDescriptionDefault
dataYes
coverageYes
evidenceNo
warningsYes
evaluatedAtYes
generatedAtYes
schemaVersionYes
datasetReleaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • addedOutput schema / properties / coverage / properties / statisticsObservations
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / coverage / properties / statisticsSubjects
      Added value: +{
      +  "type": "number"
      +}
  2. First observedv0.1.1

TDQS

C2.7/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful caveats beyond that: preserve evidence dates, conditions, coverage gaps, and warnings, and do not treat missing context as establishing eligibility or a waiver.

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?

The description is short and front-loaded, with no wasted sentences. The phrasing is somewhat cryptic, but the structure is efficient for the small amount of content it provides.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. However, for an eight-parameter tool with zero schema description coverage, the description is incomplete: it omits parameter meaning, usage context, and any explanation of what the retrieved travel rule includes.

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

Parameters1/5

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

The schema has eight parameters with 0% description coverage, including two enums and several pattern-constrained strings. The description provides no information about what passport, destination, include, purpose, release, transport, documentType, or qualifyingVisa mean or how to use them.

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

Purpose3/5

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

The description says 'Read-only get travel rule,' which names a verb and resource but largely restates the tool name and the read-only annotation. It does not explain what a travel rule contains or how it differs from sibling tools like get_coverage or get_programme.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, nor any stated prerequisites or context requirements. The eligibility caveat is a warning, not usage guidance.

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