Skip to main content
Glama

mcp-server

by io.github.roamzy-io
OverviewAdmin

roamzy_list_countries

Read-onlyIdempotent

List all 193 countries with Roamzy per-MB rates in USDT — reference table of roaming rates. The user gets one universal eSIM; this list is the rate card, not a product catalog. Call this only if the user asks «what countries are supported» or «show me rates» — don't volunteer it during a purchase flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
coverageNo
currencyNo
countriesYes
api_versionNo
prices_versionNoTariff revision the rates come from, e.g. "01082026".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "api_version": {
+      "type": "string"
+    },
+    "countries": {
+      "items": {
+        "properties": {
+          "flag": {
+            "type": "string"
+          },
+          "is_premium": {
+            "type": "boolean"
+          },
+          "iso_alpha_2": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rate_usdt_per_gb": {
+            "type": "number"
+          },
+          "rate_usdt_per_mb": {
+            "type": "number"
+          },
+          "slug": {
+            "description": "Identifier accepted by the other tools, e.g. \"esim-japan\".",
+            "type": "string"
+          },
+          "zone": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "coverage": {
+      "properties": {
+        "total_countries": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "prices_version": {
+      "description": "Tariff revision the rates come from, e.g. \"01082026\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "countries"
+  ],
+  "type": "object"
+}
  2. 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 destructiveHint. The description adds context that this is a reference rate card, not a product catalog, and should not be volunteered during purchase. This complements the annotations without contradicting them.

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?

The description is two sentences, front-loaded with the primary function, and each sentence adds distinct useful information. No wasted words.

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 zero-parameter, read-only list with an output schema and strong annotations, the description is complete. It covers purpose, usage constraints, and context, leaving no critical information 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 tool has zero parameters, so the description has no parameter documentation burden. Baseline 4 applies because schema coverage is trivially 100%.

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 clearly states it lists all 193 countries with per-MB rates in USDT, a specific verb and resource. It distinguishes itself from a product catalog and the purchase flow, aligning with sibling tools like roamzy_country_detail.

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 explicitly states when to call ('only if the user asks «what countries are supported» or «show me rates»') and when not to call ('don't volunteer it during a purchase flow'). It does not name alternative tools directly, but the when-not clause provides strong guidance.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources