mcp-server

roamzy_status

Read-onlyIdempotent

Check Roamzy API status, including agent pause flags. Agents MUST call this before purchase attempts and back off if purchases_paused=true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`time`	No	ISO-8601 server time.
`reason`	No	Operator note when something is paused; null otherwise.
`anon_paused`	No	When true, anonymous sessions are not being minted.
`api_version`	Yes
`agents_paused`	Yes	When true, back off entirely.
`purchases_paused`	Yes	When true, do not attempt roamzy_create_order.

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": {
+    "agents_paused": {
+      "description": "When true, back off entirely.",
+      "type": "boolean"
+    },
+    "anon_paused": {
+      "description": "When true, anonymous sessions are not being minted.",
+      "type": "boolean"
+    },
+    "api_version": {
+      "type": "string"
+    },
+    "purchases_paused": {
+      "description": "When true, do not attempt roamzy_create_order.",
+      "type": "boolean"
+    },
+    "reason": {
+      "description": "Operator note when something is paused; null otherwise.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "time": {
+      "description": "ISO-8601 server time.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "api_version",
+    "agents_paused",
+    "purchases_paused"
+  ],
+  "type": "object"
+}

First observedMay 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the critical behavioral detail about the `purchases_paused` flag and the expected 'back off' action, which goes beyond simple status checking. It does not contradict annotations.

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 two sentences: the first states the purpose, the second delivers a mandatory action. No filler words, no repetition of schema or annotation content. Every word 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 status check with an output schema present, the description fully covers the necessary context: what is checked, the key flag to look for, and the required action. The sibling tools and annotations provide additional context, but nothing essential is missing.

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

Parameters4/5

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

The tool has zero parameters, and the baseline for 0-parameter tools is 4. The description focuses on the response field (`purchases_paused`) rather than input semantics, which is appropriate given there is nothing to document about parameters.

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 states a specific verb ('Check') and resource ('Roamzy API status'), and clarifies the scope by mentioning 'agent pause flags'. This clearly distinguishes it from sibling tools like purchase or order operations, which are about actions rather than status.

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 explicitly says 'Agents MUST call this before purchase attempts and back off if `purchases_paused=true`'. This provides a clear precondition and behavioral instruction, making it undeniable when to use this tool versus proceeding with a purchase.

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.