Skip to main content
Glama

What is blocked in a country

blocked_services
Read-only

Whether WhatsApp / Telegram / Viber calls, FaceTime, messages, social media, YouTube, Google, VPN and streaming work in a country (43 travel destinations), each fact with its source, date and confidence (verified or not), what to do, Ukrainian banking apps abroad. Tutu eSIM is data only and promises no bypass of local blocks.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the notes (default en)
countryYesISO 3166 code (AE, EG) or the name in English, Ukrainian or Russian

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "uk",
      -  "ru"
      -]New value: +[
      +  "en",
      +  "uk",
      +  "ru",
      +  "pl",
      +  "de",
      +  "es",
      +  "fr",
      +  "it",
      +  "nl"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, the description discloses that each fact carries a source, a date, and a verified-or-not confidence marker, and it bounds coverage to 43 travel destinations. That is meaningful behavioral context an agent cannot get from the annotations. It does not say how staleness is handled or what happens for an unsupported country.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the whole thing is one comma-spliced run-on sentence mixing service lists, confidence metadata, the Ukrainian banking aside, and an eSIM disclaimer. It is not padded with filler, yet the structure makes it harder to parse than it needs to be.

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 two-parameter read-only lookup with no output schema, the description conveys what comes back (per-service verdicts plus source, date, confidence) and the geographic scope limit. The slight gap is the unexplained 'Ukrainian banking apps abroad' clause and no guidance for countries outside the 43.

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 the country format (ISO code or name in English/Ukrainian/Russian) and the lang enum are already documented. The description adds the fact that the country set is limited to 43 destinations and that lang governs 'notes', but adds nothing about format or defaults. Baseline 3 applies.

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?

The description names a concrete question - whether specific services (WhatsApp/Telegram/Viber calls, FaceTime, social media, YouTube, Google, VPN, streaming) work in a given country - which is clearly distinct from the pricing/roaming/plan siblings. It is specific about the resource even though it never explicitly contrasts itself with a sibling tool.

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?

Usage is only implied: an agent can infer this is for pre-travel connectivity checks. There is no explicit 'use this when...' or statement of when a sibling like get_country or roaming_cost is the better choice. The closing note that 'Tutu eSIM is data only and promises no bypass of local blocks' functions as a partial when-NOT caveat, which lifts it above purely implied guidance.

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