Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Public Status

getPublicStatus
Read-only

Retrieve public status data for a Cloady app using its workspace and app slug, with optional environment selection; no token is required for public access.

Instructions

The data behind https://cloady.com/status/{workspaceSlug}/{appSlug}. Public: no token needed. env reads a preview or development app; production by default. Answers 404 when there is no such app.

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": "getPublicStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
appSlugYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, and non-destructive traits, yet the description adds real behavior: it is anonymously accessible, defaults to production, and returns 404 when the app does not exist. That error and default behavior is exactly the kind of information annotations cannot express.

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, front-loaded with the resource identity, then access mode, then parameter default, then error behavior. No filler and no repetition of the title.

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?

For a simple three-parameter read with no output schema, the description covers access, defaulting, and the 404 failure mode, which is enough to call it correctly. It does not hint at the shape of the returned status data or any rate limiting, a minor omission for a public endpoint.

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 coverage is 0%, so the description carries the burden; it explains `env` well (preview/development vs. default production), and the URL template implies workspaceSlug and appSlug are path segments. The two required slug parameters are still only described by their names, leaving their format and lookup semantics unstated.

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?

The description states a specific resource — the data backing the public status page at cloady.com/status/{workspaceSlug}/{appSlug} — so an agent knows it returns status-page content. It implicitly distinguishes itself from private tooling by noting 'Public: no token needed,' but it never names the close sibling getStatusPage, so an agent must infer the difference.

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?

It gives useful calling context: no token is required, and `env` selects a preview/development app with production as the default. It does not say when to prefer this over getStatusPage or other status-related siblings, so the when-to-use decision is only implied.

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