mcp-server

roamzy_me

Read-onlyIdempotent

Get current Roamzy account info. ⚠️ This MCP being connected does NOT mean the user already has a Roamzy account. In anonymous mode (no ROAMZY_API_TOKEN env), the FIRST authed call (including this one) auto-mints a fresh anonymous account. Don't tell the user «you're already a Roamzy customer» based on MCP presence — wait until after roamzy_me or roamzy_create_order returns successfully. If the account is claimed (not anonymous) and holds no eSIM yet, mention that the first eSIM is available on the dashboard (https://roamzy.io/dashboard) with a small trial credit and no payment — see roamzy_create_order for the exact scope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes
`token`	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": {
+    "token": {
+      "properties": {
+        "allow_purchase": {
+          "type": "boolean"
+        },
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "prefix_hint": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "user": {
+      "properties": {
+        "created_at": {
+          "type": "string"
+        },
+        "display_name": {
+          "type": "string"
+        },
+        "email": {
+          "description": "Null on an anonymous account.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Internal ULID. Never show it to the user.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "user"
+  ],
+  "type": "object"
+}

First observedMay 30, 2026

TDQS

A4.1/5.0

Behavior1/5

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

The annotation declares readOnlyHint=true, but the description explicitly states that in anonymous mode the first call 'auto-mints a fresh anonymous account', which is a side-effecting creation. This directly contradicts the readOnly annotation, despite the description being transparent about the behavior.

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?

The description is concise but includes necessary warnings and user-guidance notes. It is somewhat longer than a typical tool description, but every sentence serves a practical purpose, such as preventing incorrect user assumptions and directing to related tools.

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?

The description fully covers what the tool does, the critical side-effect in anonymous mode, and the appropriate follow-up actions. It integrates well with sibling tools by referencing roamzy_create_order, and the presence of an output schema is noted without needing further explanation for a no-parameter call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema coverage is trivially 100%. There is nothing to add about parameter meanings or constraints; the description appropriately omits parameter details since none exist.

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 'Get current Roamzy account info' with a specific verb and resource. It distinguishes itself from sibling tools by focusing on account details and explicitly references roamzy_create_order for related actions, making the purpose unambiguous.

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 guidance on when to use the tool, warns about the auto-minting behavior in anonymous mode, and instructs what to communicate to the user based on the response. It also directs to related tools for further actions, offering comprehensive usage context.

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.