mcp-server

roamzy_country_detail

Read-onlyIdempotent

Reference info: the per-MB rate for a specific country. Call ONLY if the user explicitly asks about price for their destination (e.g. «how much in Japan?»). DO NOT call this during purchase — the user does not need to pick a country to buy. The eSIM works in all 193 countries; rates are reference info, not a purchase gate.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country_slug`	Yes	Country slug, e.g. "esim-spain". Reference lookup only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`country`	Yes
`api_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "api_version": {
+      "type": "string"
+    },
+    "country": {
+      "properties": {
+        "flag": {
+          "type": "string"
+        },
+        "is_premium": {
+          "type": "boolean"
+        },
+        "iso_alpha_2": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "page_url": {
+          "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"
+    }
+  },
+  "required": [
+    "country"
+  ],
+  "type": "object"
+}

First observedMay 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds non-obvious behavioral context: the eSIM works in all 193 countries and rates are reference info, not a purchase gate. This prevents an agent from misusing a country lookup as a purchase prerequisite.

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?

Three tight sentences, front-loaded with the purpose and followed by the guardrail and rationale. Every sentence earns its place with no redundancy.

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?

An output schema exists, so return values need no explanation. Given the simple single-param lookup, the description supplies everything an agent needs to decide whether and how to call it.

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 coverage is 100% with a single country_slug parameter whose format is documented ('esim-spain'). The description adds only the notion of a country lookup and does not extend parameter semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: the per-MB rate for a specific country, delivered as reference info. It is clearly distinguishable from siblings like roamzy_list_countries and roamzy_estimate by naming the exact lookup being performed.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Call ONLY if the user explicitly asks about price for their destination'), a concrete example, and a when-not ('DO NOT call this during purchase'). It even explains the rationale that the user needs no country selection to buy.

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

All mcp-server tools Inspect

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.