SqueezeOS — Institutional AI Market Intelligence

System Status

system_status

Read-onlyIdempotent

Read the live SqueezeOS status endpoint. Use this when an agent needs a quick health check of the API host before starting paid work. Returns the live status payload; the MCP server never synthesizes cluster-health or synchronization claims. Read-only and idempotent; no side effects. On error, returns a structured error. For example, check status first if paid calls start timing out.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Whether the upstream HTTP status is 2xx; not settlement proof.
`body`	No	Unmodified upstream JSON, or bounded response text. Consult that capability's live schema.
`error`	No
`charged`	No	Present on local/transport failures; these do not establish an upstream charge.
`message`	No
`auto_spent`	No
`status_code`	No	Observed upstream HTTP status, or null when no response was obtained.
`substituted`	No
`content_type`	No
`payment_required`	No	Observed PAYMENT-REQUIRED header; a challenge does not prove payment.
`payment_response`	No	Observed PAYMENT-RESPONSE header. Assess it together with accepted delivery.
`caller_supplied_authorization`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "status_code"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Canonical REST response envelope, or a local/transport rejection. Upstream data remains in body and is defined by the live capability schema.",
+  "properties": {
+    "auto_spent": {
+      "const": false
+    },
+    "body": {
+      "description": "Unmodified upstream JSON, or bounded response text. Consult that capability's live schema."
+    },
+    "caller_supplied_authorization": {
+      "type": "boolean"
+    },
+    "charged": {
+      "const": false,
+      "description": "Present on local/transport failures; these do not establish an upstream charge."
+    },
+    "content_type": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the upstream HTTP status is 2xx; not settlement proof.",
+      "type": "boolean"
+    },
+    "payment_required": {
+      "description": "Observed PAYMENT-REQUIRED header; a challenge does not prove payment.",
+      "type": "string"
+    },
+    "payment_response": {
+      "description": "Observed PAYMENT-RESPONSE header. Assess it together with accepted delivery.",
+      "type": "string"
+    },
+    "status_code": {
+      "description": "Observed upstream HTTP status, or null when no response was obtained.",
+      "maximum": 599,
+      "minimum": 100,
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "substituted": {
+      "const": false
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJun 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description still adds real behavioral context: the server never synthesizes cluster-health or synchronization claims, and errors return a structured payload. It does not discuss caching or rate limits.

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?

Front-loaded with purpose, then usage, then behavior; nearly every clause carries weight. The closing timeout example partly repeats the earlier 'before starting paid work' guidance, which keeps it short of a 5.

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 parameterless read tool with an output schema, the description covers purpose, trigger, read-only semantics, the no-synthesis guarantee, and error behavior. Nothing an agent needs to call it correctly is missing, and return values are already documented by the output schema.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. Schema coverage is 100% with additionalProperties false, so no compensating detail is required.

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?

States a specific verb (read) and resource (the live SqueezeOS status endpoint), and the scope 'live status endpoint' distinguishes it from every sibling capability/quote/verify tool. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use condition ('quick health check of the API host before starting paid work') plus a concrete trigger ('check status first if paid calls start timing out'). It does not name an alternative sibling or state when not to use it, but no sibling overlaps this preflight role.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SqueezeOS — Institutional AI Market Intelligence 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.