Skip to main content
Glama

connect_workspace

Completes a SpecPlanner panel connection request using the exact requestId and this chat's trusted project directory, so the waiting panel updates automatically.

Instructions

Complete the connection request from a SpecPlanner panel in THIS chat. Use the exact requestId from the panel's message and this chat's trusted absolute project directory. Never infer from another chat or the plugin installation. Pass null only if this chat has no project directory. Do not call open_planner again; the waiting panel will update automatically.

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": {
      "requestId": "<requestId>",
      "workspacePath": "<workspacePath>"
    },
    "name": "connect_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes
workspacePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds real behavioral context beyond that: the panel self-updates, open_planner must not be re-invoked, and the null path is scoped. It stops short of describing what state is actually created or how an invalid/stale requestId fails, which is a gap for a mutation tool.

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?

The core action and the identity of the correct requestId are front-loaded, then constraints follow in descending priority. Every sentence carries a distinct constraint (source of requestId, source of path, null case, follow-up behavior) with no filler.

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 and only two required parameters, the definition covers both inputs, the invocation context, and post-call expectations. The remaining gap is failure behavior: what happens with a stale requestId or a non-absolute path, and what 'connected' concretely means, is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry both parameters, and it does: requestId must be the exact value from the panel's message and must not be inferred from another chat or the plugin installation; workspacePath is this chat's trusted absolute project directory, with null permitted only when no project directory exists. This is far richer than the bare string/null schema.

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 verb and resource: 'Complete the connection request from a SpecPlanner panel in THIS chat.' It also explicitly distinguishes itself from the sibling open_planner by telling the agent not to call it again, so an agent can tell the two apart without inspecting schemas.

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 explicit when-to-use ('from a SpecPlanner panel in THIS chat'), explicit when-not ('Never infer from another chat or the plugin installation'), and an explicit alternative path ('Do not call open_planner again; the waiting panel will update automatically'). Very little is left to inference.

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