listAppDomainsRetrieve all domains assigned to an app in a workspace. Use this to view and manage domain configurations for your Cloady deployments.
List all domains for an app in a workspace
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| region | No | ||
| appSlug | Yes | ||
| workspaceSlug | Yes |
Changes observed during successful MCP inspections.
v0.5.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description's 'list' wording is consistent with the readOnlyHint annotation. However, it adds no extra transparency about pagination, output limits, or potential errors beyond what the annotations already convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that efficiently conveys the purpose without unnecessary verbiage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description implies the return is a list of domains but does not specify the output structure, possible error cases, or required permissions. For a simple list operation, this may be adequate but lacks completeness without an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no descriptions for any parameters (0% coverage), and the description only mentions the resource scope without elaborating on the optional env and region parameters or their filtering semantics. The parameter names are somewhat self-explanatory but not fully clear.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (list) and the resource (all domains for an app in a workspace). It distinguishes itself from the sibling tool listWorkspaceDomains, which presumably lists domains at the workspace level.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus similar tools such as listWorkspaceDomains, nor are any prerequisites or context given for choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.