mcp-server

roamzy_estimate

Read-onlyIdempotent

Reference calculation: how many USDT a given MB volume would cost at a given country's rate. ONLY for informational «how much would 2GB in Japan cost» queries. DON'T use this to gate a purchase — the user doesn't pre-buy data volumes. They fund a USDT balance and pay per actual MB.

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_slug": "<country_slug>",
      "mb_estimated": "<mb_estimated>"
    },
    "name": "roamzy_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`country_slug`	Yes	Country slug for rate lookup, e.g. "esim-spain". Reference only.
`mb_estimated`	Yes	Hypothetical MB volume for the «how much would X cost» reference calc.

Output Schema

Name	Required	Description	Default
`input`	No
`result`	Yes
`country`	No
`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": {
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "input": {
+      "properties": {
+        "mb_estimated": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "properties": {
+        "amount_usdt": {
+          "description": "What that volume would cost at this rate.",
+          "type": "number"
+        },
+        "min_topup_usdt": {
+          "description": "Floor on any real top-up, independent of the estimate.",
+          "type": "number"
+        },
+        "must_top_up_at_least": {
+          "type": "number"
+        },
+        "rate_usdt_per_mb": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedMay 30, 2026

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, so the safety profile is covered. The description adds valuable behavioral context: the tool is purely informational, depends on country-specific rates, and must not be used as a sales gate. 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.

Conciseness5/5

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

The description is three sentences with the core purpose front-loaded in the first sentence. The second and third sentences deliver crucial usage constraints without redundancy. Every sentence earns its place, making it both concise and well-structured.

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?

With an output schema, rich annotations, and a clear behavioral boundary (informational only), the description is fully complete for an agent to select and invoke the tool correctly. It covers what, when, and why-not, leaving no significant gaps.

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?

Both parameters are fully described in the input schema (100% coverage), with examples. The description does not add new parameter-level meaning beyond reinforcing the 'reference' nature, so the baseline of 3 is appropriate given schema coverage.

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 performs a reference calculation: estimating the USDT cost of a given MB volume at a country's rate. It uses a specific verb ('calculation') and explicitly differentiates from sibling tools by noting it's informational and not a purchase gate. This leaves no ambiguity about what the tool does.

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?

The description provides explicit when-to-use guidance ('ONLY for informational queries') and when-not-to-use guidance ('DON'T use this to gate a purchase'), with the underlying rationale about the user's funding model. This is exemplary alternative/contextual direction for an agent.

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.