Skip to main content
Glama

mcp-server

by io.github.roamzy-io
OverviewAdmin

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; rates are reference info, not a purchase gate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_slugYesCountry slug, e.g. "esim-spain". Reference lookup only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes
api_versionNo

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"
+    },
+    "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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context: rates are reference info only, not a purchase gate, and the eSIM works in all 193 countries. This goes beyond 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.

Conciseness4/5

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

Four sentences, front-loaded with 'Reference info' and a clear purpose. Each sentence adds meaningful guidance (when to call, when not to call, why not). Slightly longer than the minimal two-sentence ideal, but every part 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 simple single-parameter read-only lookup with an output schema, the description fully covers purpose, usage constraints, and context. No significant gaps remain for an AI agent to invoke it correctly.

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 clear description of country_slug ('Country slug, e.g. "esim-spain". Reference lookup only.'). The tool description reinforces the reference nature but does not add new parameter-level details, so the baseline of 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?

The description clearly states the tool provides 'the per-MB rate for a specific country.' It explicitly positions it as reference info, distinguishing it from purchase-related siblings like roamzy_create_order. The example about 'how much in Japan?' reinforces the exact purpose.

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?

Explicitly instructs to call 'ONLY if the user explicitly asks about price for their destination' and includes a strong exclusion: 'DO NOT call this during purchase.' This leaves no ambiguity about when to use this tool versus alternatives.

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