eSIM MCP Server

Get eSIM plan details

get_bundle_details

Read-onlyIdempotent

Retrieve complete details for a specific eSIM plan, including data, validity, price, coverage, plan type, activation policy, and availability, to provide in-depth information about a plan the user selected.

Instructions

Read the full details of one plan: data, validity, price, coverage, plan type, activation policy and availability. WHEN: the user asks about a specific plan you already listed -- "tell me more about the second one". Pass the bundle_code of the option the user picked, taken from the result you already have. Never invent a code, and never ask the user to read one out. AFTER SUCCESS: describe the plan in ordinary language and pass on the price note: the displayed catalogue price may not include final tax. Nothing here reserves, orders or charges anything -- this version cannot buy a plan. This needs no login.

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": {
      "bundle_code": "<bundle_code>"
    },
    "name": "get_bundle_details"
  }
}

Input Schema

Name	Required	Description
`locale`	No	Optional language tag for platform text, e.g. 'en'. Omit to use the server default.
`currency`	No	Optional ISO-4217 currency code, e.g. 'USD'. Omit to use the server default.
`bundle_code`	Yes	The bundle_code of a plan from a result you have already received. Never invent, guess or edit one, and never ask the user to read one out -- if you do not have it, search again and use the code from the option the user picked.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnlyHint and idempotentHint true; the description reinforces this by stating 'Nothing here reserves, orders or charges anything'. It also adds context about no login required and a price tax caveat, going beyond the annotations without contradicting them.

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?

Organized with purpose, WHEN, and AFTER SUCCESS sections. Front-loaded with the main action and every sentence adds useful operational or behavioral information without fluff.

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

Completeness5/5

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

With an output schema present, return-value details are not needed. The description covers purpose, usage, parameter source, side-effect profile, and even a pricing nuance, making it fully complete for this simple read tool.

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 description coverage is 100% and the description's guidance for bundle_code largely repeats the schema's own description ('from a result you have already received; never invent'). It does not add significant meaning beyond what the schema already provides, so the baseline 3 applies.

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?

Description states 'Read the full details of one plan' and lists the specific fields (data, validity, price, coverage, plan type, activation policy, availability). This uses a specific verb (Read) and resource, and clearly distinguishes from sibling tools like browse/find by focusing on a single plan already listed.

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

Usage Guidelines5/5

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

Explicitly provides a usage condition: 'WHEN: the user asks about a specific plan you already listed'. It instructs to pass the bundle_code from existing results and never invent one, and also states that this tool does not buy or reserve anything, guiding away from purchase use cases.

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