Skip to main content
Glama

LibrePass eSIM

List eSIM packages

list_packages
Read-onlyIdempotent

List the eSIM packages for one country: data volume, validity, speed, price in EUR (VAT included), daily plans, the monthly pool and the mobile networks used. Each fixed package and the monthly pool has a url that opens the country page with that plan selected.

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": "<country>"
    },
    "name": "list_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry id, ISO code or English name, e.g. "tr", "TH", "United Kingdom"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond them: prices are in EUR with VAT included, daily plans and the monthly pool exist, and fixed packages/monthly pool each carry a deep-link url. It omits anything on result ordering or size limits, but for a read-only listing that is a minor gap.

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?

Two front-loaded sentences with no filler; the purpose leads and the field list follows. The second sentence about per-plan urls is narrower detail but still earns its place by explaining an otherwise unexpected return element.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so by enumerating the package attributes and the embedded url. It stops short of stating the response container shape or whether results are ever truncated, which keeps it from full marks.

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 single country parameter already documents accepted forms (ISO code, id, English name) with examples. The description only restates 'for one country', adding no new meaning; baseline 3 is appropriate.

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?

States a specific verb and resource with scope: 'List the eSIM packages for one country', then enumerates the fields returned (data volume, validity, speed, price, daily plans, monthly pool, networks). An agent can distinguish this from get_package by the plural/list framing, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The country scoping implies when this tool applies (browsing options for a destination), but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_package for a single plan's detail. Usage must be inferred rather than read.

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