Skip to main content
Glama

OsmO Travel eSIM

Show before-you-fly checklist

show_before_you_fly
Read-onlyIdempotent

Shows the before-you-fly checklist as an interactive card.

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": "show_before_you_fly"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdNo
platformNo
destinationNo
departureDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's only added behavioral signal is that output is presented as an interactive card rather than raw data, which is useful but thin; nothing is said about what the card contains or what happens when parameters are omitted.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but at this length conciseness shades into under-specification given four undocumented parameters and a sibling with a near-identical name. It is efficient but does not earn its brevity.

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?

With four optional parameters, no output schema, and 0% schema description coverage, the definition leaves key questions unanswered: what the card shows, whether omitting parameters yields a default checklist, and how it differs from get_before_you_fly_checklist. Annotations cover safety only, so the description should carry more of this load.

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?

Schema description coverage is 0% across four parameters (planId, platform, destination, departureDate), and the description supplies no meaning for any of them. With all four undocumented and zero optional/required guidance in prose, the description fails the burden it carries when schema coverage is this low.

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 pairs a specific verb ('Shows') with a specific resource ('the before-you-fly checklist') and adds a rendering hint ('as an interactive card') that implicitly separates it from the sibling get_before_you_fly_checklist. It never names that sibling or states the distinction explicitly, so an agent must infer whether this returns data or renders UI.

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 call this versus get_before_you_fly_checklist or any of the other show_* card tools. The phrase 'interactive card' hints at presentation, but no condition, prerequisite, or exclusion is stated.

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