BuyUKeSIM — eSIM & UK Number MCP

search_esim_plans

Search BuyUKeSIM travel/data eSIM plans for a country. Returns plan name, data amount, validity days, USD price, package code and a buy link that opens checkout on that exact plan. Structured output adds, per plan: covered countries, local carriers, 5G, top-up support, hotspot (allowed on every plan) and the country traffic exits in. A feature the supplier does not state is null (unknown), never false. Pass a 2-letter ISO country code (e.g. GB, US, TR, JP). Omit country to get popular/featured plans. Data only: no phone number, no SMS (for that see get_uk_number_info).

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max plans to return (1-50). Default 20.
`country`	No	2-letter ISO country code, e.g. GB, US, TR, JP. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it lists returned fields, states the buy link opens checkout on the exact plan, and defines the null-means-unknown convention (never false). It does not state rate limits, whether results are cached/live, or ordering/pagination behavior beyond the limit parameter.

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?

Front-loaded with purpose and usage, then the return contents and the null semantics. The enumeration of structured fields and per-plan attributes is dense and slightly list-like, but each clause carries information an agent would otherwise lack.

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?

There is no output schema, and the description compensates by enumerating the return fields and the null convention, plus what each plan covers. For a two-parameter read/search tool, nothing an agent needs to call it correctly is missing.

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 100%, so the schema already documents both parameters, and the baseline is 3. The description adds the omit-country behavior (return popular/featured plans) and reinforces the ISO format with examples, but adds nothing about the limit parameter beyond what the schema already says.

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?

States a specific verb and resource ('Search BuyUKeSIM travel/data eSIM plans') and scopes it to a country. It also explicitly contrasts itself with get_uk_number_info for phone numbers/SMS, so an agent can separate it from the number-related siblings without opening any schema.

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?

Gives a concrete usage rule: pass a 2-letter ISO code for a country, omit it for popular/featured plans, and redirects the number/SMS use case to get_uk_number_info. It stops short of naming the natural follow-on tool (e.g. purchase_esim) or distinguishing itself from list_covered_countries/get_esim_exit_countries, which are adjacent in purpose.

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

All BuyUKeSIM — eSIM & UK Number MCP tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?