Skip to main content
Glama

OsmO Travel eSIM

Before-you-fly checklist

get_before_you_fly_checklist
Read-onlyIdempotent

Use this when the user asks what to do before travelling so they have mobile data on arrival.

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

Input Schema

NameRequiredDescriptionDefault
planIdNo
platformNo
destinationNo
departureDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavior beyond the trigger — it does not say the result is a static checklist, whether it varies by destination or platform, or whether any parameters are required to get a useful answer.

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?

A single efficient sentence with the triggering condition front-loaded and no wasted wording. It is lean to a fault: the space saved is not reallocated to stating what the tool actually returns.

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 undocumented optional parameters and no output schema, the description should explain what the checklist covers and how the parameters shape it; it does neither. An agent can decide to call it, but cannot confidently populate or omit parameters, nor predict the response.

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

Parameters2/5

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

All four parameters (planId, platform, destination, departureDate) have 0% schema description coverage, so the description carries the full burden and supplies nothing. Only weak inference is possible — 'before travelling ... on arrival' hints at destination/departureDate, and 'mobile data' hints at planId — but an agent gets no explanation of what providing or omitting each parameter changes.

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 sentence is framed as a trigger ('Use this when the user asks what to do before travelling') rather than as a statement of what the tool returns; the only signal that it produces a checklist comes from the name and title. It is understandable, but it does not distinguish itself from the sibling 'show_before_you_fly', and the actual output (a preparation checklist) is never stated.

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?

It gives an explicit, actionable trigger: the user asks what to do before travelling to have mobile data on arrival. There are no explicit exclusions or named alternatives, but the when-to-use condition is concrete enough to route most calls correctly.

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