Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Stream App Status

streamAppStatus
Read-only

Read an app's live status—per-service state, capacity waits, and in-flight deploy—or stream updates every five seconds via text/event-stream.

Instructions

Read an app's live status: per-service state, capacity waits, in-flight deploy. Returns one status frame. Sending Accept: text/event-stream instead follows the status live, a frame every five seconds, which never completes on its own.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>"
    },
    "name": "streamAppStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.8/5.0
Behavior5/5

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

Annotations cover safety (readOnly, non-destructive) and openness, and the description adds behavior those annotations cannot express: one frame by default versus an SSE stream at five-second intervals that never terminates. The non-termination warning is exactly the operational detail an agent needs to avoid hanging on the call.

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 sentences, front-loaded with the primary behavior, then the return cardinality, then the streaming variant. No filler, and the most consequential constraint (never completes on its own) is placed last where it still reads clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately explains what a response contains and how many frames come back, and it clarifies the streaming mode. The remaining gap is the entirely undocumented input parameters, which is notable for a four-parameter tool.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden - yet it never mentions env, region, workspaceSlug, or appSlug. The enum values for env and the meaning/format of region are undocumented everywhere, leaving half the inputs ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read an app's live status" gives a specific verb and resource, and the enumerated payload (per-service state, capacity waits, in-flight deploy) makes the scope concrete. It does not explicitly name a sibling to route away from, though the content implicitly distinguishes it from streamAppMetrics or streamActiveDeploy.

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

Usage Guidelines3/5

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

The description explains the two invocation modes and how to switch between them (Accept: text/event-stream), which is genuine usage guidance. It gives no guidance on when to prefer this over streamActiveDeploy, streamAppMetrics, or getAppServices, so sibling selection is left to inference.

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

Deploy Server

Other Tools