Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

List Workspace Domains

listWorkspaceDomains
Read-only

Retrieve every custom domain for a workspace, including renewal details and whether an application serves it, to audit domain coverage and registrations.

Instructions

Every custom domain the workspace's applications serve, and every domain registered through Cloady, with its renewal details, whether or not an application serves it.

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>"
    },
    "name": "listWorkspaceDomains"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the agent knows the safety profile without the description. The description adds genuine context by saying the result includes unserved and third-party-registered domains with renewal data, which is non-obvious. It says nothing about pagination, result limits, or permission requirements for the workspace scope.

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?

A single sentence that front-loads the union of domain sources and adds the return-content hint (renewal details). The trailing 'whether or not an application serves it' restates the earlier distinction between app-served and merely registered domains, so there is minor redundancy.

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 carries the burden of describing results, and it does name the two domain sources plus renewal details. For a one-parameter read tool whose annotations cover the safety profile, this is nearly complete; only pagination/volume expectations and renewal-detail fields remain unstated.

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?

There is a single parameter, workspaceSlug, with 0% schema description coverage, so the schema contributes nothing about its format or meaning. The description refers to 'the workspace's applications' and Cloady-registered domains, which implies the parameter scopes the inventory to one workspace, but it never states slug format or behavior for an invalid or inaccessible slug.

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 identifies a specific resource and scope: custom domains served by the workspace's applications plus domains registered through Cloady, including renewal details. The clause 'whether or not an application serves it' implicitly distinguishes it from the app-scoped sibling listAppDomains, though it never names that sibling. It lacks an explicit verb like 'List', but the resource is unmistakable.

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?

Usage is only implied by the stated scope: an agent can infer the tool is for a workspace-wide domain inventory rather than a per-app view. There is no explicit 'use this when' guidance, no mention of alternatives such as listAppDomains or checkDomains, and no prerequisites stated.

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