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.

Input Schema

TableJSON 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

TableJSON Schema

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

Schema Changelog

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

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=true and destructiveHint=false. The description adds valuable context about the tool being purely informational and warns against using it for purchase gating, which goes beyond the annotation hints.

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 short sentences with no filler. The first sentence states purpose, the second gives usage context, and the third provides a clear exclusion. Highly efficient.

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?

Given the tool's simplicity, two well-documented parameters, and an output schema, the description fully covers purpose, usage boundaries, and business logic. No gaps identified.

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 baseline is 3. The description reinforces the reference-only nature of the parameters but does not add significant detail beyond the schema.

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 identifies the tool as a reference calculation for converting MB volume to USDT cost at a given country's rate. It distinguishes from siblings by emphasizing it is informational only, not for order creation or management.

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 states when to use ('how much would 2GB in Japan cost' queries) and when not to use ('DON'T use this to gate a purchase'), with a clear explanation of the funding model.

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

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.