RunWhen Platform MCP

List Workspaces

list_workspaces

List all workspaces you can access, returning names, display names, and basic metadata to identify available environments.

Instructions

List all workspaces you have access to.

Returns workspace names, display names, and basic metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workspaces"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that results are limited to workspaces the caller can access and that no filtering is applied. It does not mention pagination, result-size expectations, ordering, or any failure/auth modes, which is a meaningful gap for a listing endpoint with no annotation coverage.

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?

Two short sentences, front-loaded with the action and scope before the return content. The second sentence partially duplicates what the output schema already conveys, so it is efficient but not maximally economical.

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 zero parameters and an output schema already documenting the returned fields, the description covers what the agent needs to select and call this tool. Only minor operational details (pagination, ordering) are absent, which is acceptable given 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 no parameters (schema coverage is 100% trivially), so per the baseline there is nothing for the description to clarify. It correctly avoids inventing filter or paging arguments that the schema does not support.

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?

States a specific verb (list) and resource (workspaces) with an explicit scope qualifier, 'you have access to', so the agent knows the result set is permission-filtered. No sibling tool competes for this action, so the lack of explicit differentiation isn't a real gap, but there's nothing that elevates it above a clear, standard listing tool.

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 intent ('get the set of workspaces available to me') is implied clearly by the name and description, and for a zero-argument listing tool that is largely sufficient. However, there is no explicit guidance on when to prefer this over e.g. get_workspace_context or search_workspace, nor any note about prerequisites such as authentication.

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

Deploy Server