Skip to main content
Glama

eSIM coverage of a country

get_country
Read-only

Which mobile networks Tutu eSIM uses in a country (4G/5G), the unlimited plans' fair-use speed, activation rules and the cheapest price.

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

Input Schema

NameRequiredDescriptionDefault
langNo
countryYesISO 3166 code or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, closed-domain read of reference data. The description adds what kind of data is returned (coverage, fair-use speed, activation rules, price), but says nothing about freshness of coverage data, currency of the price, or whether results are per-plan or per-country aggregate.

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?

One compact sentence, front-loaded with the core object (mobile networks) and then the supplementary fields. It is a fragment rather than a full sentence, but nothing is redundant and it scans quickly.

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

Completeness3/5

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

With no output schema, the description carries the burden of saying what comes back, and it does list the four content areas. However, it leaves the shape ambiguous — is 'cheapest price' per plan, in which currency, and how do the unlimited-plan fair-use rules relate to the network list — which matters for an agent deciding between this and compare_prices.

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?

Only two parameters; the schema documents 'country' as ISO 3166 code or name and constrains 'lang' with an enum, so most semantics come from structured data. The description never mentions either parameter, but it does not need to — the schema already covers the ambiguous one (country codes) and the enum self-documents the other.

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?

It names the resource precisely (a country's Tutu eSIM coverage) and enumerates what is returned: mobile networks with 4G/5G, unlimited-plan fair-use speed, activation rules, and cheapest price. That is specific enough to separate it from search_plans or compare_prices, though it never explicitly contrasts itself with those siblings and the 'cheapest price' element creates some apparent overlap with compare_prices.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusions, and no named alternative — the description is a content list only. An agent must infer that this is the country-lookup tool rather than a price comparison or plan search, and must guess how to handle the overlapping 'cheapest price' capability.

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