Skip to main content
Glama
Sign In

eSIM Kenya

by com.esimkenya
OverviewDiscussionsAdmin

Get eSIM provider details and plans

get_esim_provider
Read-onlyIdempotent

Get full details for a single eSIM provider by slug, including its review summary/verdict, key facts, FAQs, and every available plan (data amount, duration, price in USD). Use list_esim_providers first to find a provider slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_esim_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProvider slug, e.g. "airalo", "holafly", "safari-esim".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful context about what the call returns, which matters especially because there is no output schema. It does not mention error cases or rate limits, but for a simple read-only lookup this is sufficient.

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?

Two sentences with no filler. The primary action and payload are front-loaded, followed by a focused usage instruction. Every word earns its place.

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?

For a one-parameter, read-only, idempotent lookup with no output schema, the description fully covers what the agent needs: how to identify the provider, what the response contains, and how to obtain the slug. Nothing essential is missing.

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

Parameters4/5

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

The schema already documents the single 'slug' parameter with concrete examples and 100% coverage. The description adds practical meaning by explaining that the slug identifies a provider and that list_esim_providers should be consulted first to obtain it, which goes beyond the raw schema definition.

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 states a specific verb and resource: 'Get full details for a single eSIM provider by slug.' It enumerates exactly what is returned (review summary, key facts, FAQs, plans) and implies the scope (single provider, not a list or comparison), distinguishing it from list_esim_providers and compare_esim_providers.

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?

The description gives an explicit usage prerequisite: 'Use list_esim_providers first to find a provider slug.' It does not explicitly contrast with compare_esim_providers, but the single-provider focus plus the list-first instruction gives an agent clear operational guidance.

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

All eSIM Kenya toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources