Skip to main content
Glama

OsmO Travel eSIM

Get eSIM plan details

get_esim_plan
Read-onlyIdempotent

Use this when the user asks about one specific plan returned by search_esim_plans: networks, 5G, ID check, when validity starts, top-ups, provider notes. Hotspot and speed limits are not in our data.

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": {
      "planId": "<planId>"
    },
    "name": "get_esim_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: it discloses the data boundary ('Hotspot and speed limits are not in our data'), which prevents the agent from promising unavailable details, and implies the planId is sourced from a prior search.

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?

One sentence, front-loaded with the usage trigger, then the field inventory, then the data-gap caveat. Every clause carries information an agent needs; there is no filler.

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?

With no output schema, the field list functions as a return-value summary, and the explicit data gap covers what the agent should not claim. The remaining gap is edge-case behavior, such as what happens when planId is invalid or the plan no longer exists.

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

Parameters3/5

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

Schema coverage is 0% and the single planId parameter carries no description, so the description has to compensate. It does add provenance ('returned by search_esim_plans'), which tells the agent where a valid ID comes from, but it says nothing about format, length, or behavior on an unknown ID.

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 ('get ... details') with the resource ('one specific plan') and enumerates the returned fields: networks, 5G, ID check, validity start, top-ups, provider notes. It ties the tool to search_esim_plans, but does not distinguish it from the sibling show_esim_plan, which reads as an almost identical operation.

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?

'Use this when the user asks about one specific plan returned by search_esim_plans' gives a clear trigger and a prerequisite (the plan must already be in a search result). It stops short of explicit exclusions, such as deferring to compare_esim_plans for multi-plan questions or to search_esim_plans when no planId exists yet.

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