Skip to main content
Glama

MeiSIM USA

Search travel eSIM plans

search_plans
Read-only

Search travel eSIM data plans for a destination country. Returns plans with data allowance, validity in days, and USD price. Use this first when a user wants mobile data for a trip (e.g. "5GB in Italy for 10 days"). Returns a plan_id to pass to get_quote / purchase.

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": {
      "country_code": "<country_code>",
      "duration_days": "<duration_days>"
    },
    "name": "search_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_gbNoMinimum data in GB. Omit to return all sizes (unlimited plans always pass).
sort_byNoResult ordering. "price" = cheapest first (default).price
country_codeYesDestination country as an ISO 3166-1 alpha-2 code, e.g. "IT" for Italy.
duration_daysYesDays of coverage needed. Plans shorter than this are filtered out.

Output Schema

NameRequiredDescriptionDefault
metaYes
plansYes
how_to_buyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description still adds real workflow context beyond that: what the result records contain and that plan_id is the key required by get_quote and purchase. It says nothing about result volume or limits, which matters given openWorldHint=true.

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?

Three short sentences, front-loaded with purpose, then usage, then return/handoff information. Every sentence carries a distinct fact and none repeat the schema or title.

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?

For a search tool with full schema coverage, an output schema, and rich annotations, the description covers purpose, entry point, and downstream handoff adequately. The one gap is that it never mentions pagination, result caps, or how many plans typically come back, which is relevant for an open-world search with no limit parameter.

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%, so country_code, duration_days, data_gb and sort_by are already fully documented in the schema, including the data_gb 'omit to return all sizes' behavior. The description only restates the intent-to-parameter mapping through its '5GB in Italy for 10 days' example, adding marginal meaning. 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?

The description leads with a specific verb and resource ('Search travel eSIM data plans for a destination country') and enumerates the returned fields (data allowance, validity in days, USD price). This distinguishes it cleanly from sibling tools like get_quote and purchase, which it explicitly positions itself upstream of.

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?

It states an explicit selection rule ('Use this first when a user wants mobile data for a trip') with a worked intent example ('5GB in Italy for 10 days'), and names the downstream alternatives by handing off plan_id to get_quote / purchase. Nothing about when to choose this over its siblings is left to inference.

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.