Capable

Show workspace setup

show_workspace_setup

Read-only

Show the workspace-setup step so the user can confirm the motion(s) you recommended, name the workspace, and save. On hosts that render interactive cards it can show a setup card with your message; the result also carries the current state and available motions, so the choice can be finished in text when no card is visible. Takes no arguments; commits via finalize_workspace_setup.

When to use: Only after you have welcomed the user, explained what a motion is, and shared your evidence-based read.

Example: Show me my setup options to confirm.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`state`	No	Same shape as start_onboarding's `state`.
`can_edit`	No
`guidance`	No
`checklist`	No
`workspace_id`	No
`import_evidence`	No	Same shape as start_onboarding's `import_evidence`.
`available_motions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed12 schema fields changedOct 19, 2026

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / available_motions / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / checklist / items / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / import_evidence / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / import_evidence / description

Added value: +"Same shape as start_onboarding's `import_evidence`."

removedOutput schema / properties / import_evidence / properties

Removed value: -{
-  "accounts": {
-    "additionalProperties": false,
-    "properties": {
-      "count": {
-        "type": "number"
-      },
-      "top": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "domain": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "industry": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "name": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "name",
-            "domain",
-            "industry"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "count",
-      "top"
-    ],
-    "type": "object"
-  },
-  "candidates": {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "domain": {
-          "type": "string"
-        },
-        "evidence": {
-          "additionalProperties": false,
-          "properties": {
-            "contacts": {
-              "type": "number"
-            },
-            "emails": {
-              "type": "number"
-            },
-            "meetings": {
-              "type": "number"
-            },
-            "product": {
-              "type": "number"
-            }
-          },
-          "required": [
-            "contacts",
-            "emails",
-            "meetings"
-          ],
-          "type": "object"
-        },
-        "qualifies": {
-          "type": "boolean"
-        },
-        "suggested_name": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "suggested_name",
-        "domain",
-        "evidence",
-        "qualifies"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "contacts": {
-    "additionalProperties": false,
-    "properties": {
-      "count": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "count"
-    ],
-    "type": "object"
-  },
-  "touches": {
-    "additionalProperties": false,
-    "properties": {
-      "meetings_90d": {
-        "type": "number"
-      },
-      "total_90d": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "total_90d",
-      "meetings_90d"
-    ],
-    "type": "object"
-  }
-}

removedOutput schema / properties / import_evidence / required

Removed value: -[
-  "accounts",
-  "contacts",
-  "touches"
-]

removedOutput schema / properties / state / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / state / description

Added value: +"Same shape as start_onboarding's `state`."

removedOutput schema / properties / state / properties

Removed value: -{
-  "framework": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "id": {
-    "format": "uuid",
-    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-    "type": "string"
-  },
-  "name": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "pipeline_stages": {
-    "items": {},
-    "type": "array"
-  }
-}

removedOutput schema / properties / workspace_id / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds real context beyond annotations: host-dependent card rendering, a text fallback path because the result carries current state and available motions, and the fact that this tool does not commit — committing happens via finalize_workspace_setup. It does not address why idempotentHint is false for a read-only presentation step, leaving a small unexplained trait.

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?

Front-loaded with what happens and the escape hatch, then the prerequisite, then an example. Slightly longer than needed — the card/text dual-path sentence is dense — but every sentence carries routing or behavioral information.

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

Completeness5/5

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

With an output schema covering the return payload and annotations covering safety, the description fills the remaining gaps: sequencing preconditions, host variability, and the handoff to the finalize tool. Nothing an agent needs to invoke it correctly is missing.

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?

Zero parameters, so the schema already settles everything; the description reinforces this with 'Takes no arguments,' which prevents an agent from hunting for inputs. Baseline 4 for a parameterless tool.

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

Purpose5/5

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

States a specific action (show the workspace-setup step) plus its purpose (confirm recommended motions, name the workspace, save) and explicitly distinguishes the commit step by naming finalize_workspace_setup as the tool that actually writes. An agent can tell it apart from its write sibling without inspecting a schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite chain — only after welcoming the user, explaining what a motion is, and sharing an evidence-based read — and names the alternative/next tool (finalize_workspace_setup) for the commit. Includes a concrete example invocation.

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

All Capable tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?