Skip to main content
Glama

Open SpecPlanner

open_planner
Read-only

Opens SpecPlanner for the active Codex project with its trusted absolute workspace path, letting users plan and review software via proposals, tasks, revision-aware comments, and a drawing board.

Instructions

Open SpecPlanner for the current Codex project. Pass its absolute project directory as workspacePath using the current chat context. Do not ask for an environment variable or use the plugin installation directory. If the chat has no project directory, omit workspacePath and let the panel offer workspace entry. Always pass the same workspacePath in subsequent tool calls.

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": "open_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspacePathNoTrusted absolute project path from this chat; pass on every call. null selects personal storage. Omission uses only the environment default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds behavior beyond that: it opens a panel that can offer workspace entry when the path is omitted, and it imposes a cross-call consistency contract ('always pass the same workspacePath in subsequent tool calls') that no annotation conveys.

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?

Purpose is front-loaded in the first clause and each following sentence carries an operational rule. Slight redundancy: 'always pass the same workspacePath in subsequent tool calls' overlaps the schema's 'pass on every call', so it is efficient but not maximally tight.

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?

For a single-optional-parameter, non-destructive tool with no output schema and full annotation coverage, the description supplies everything an agent needs: how to obtain the path, the omission fallback, and persistence across calls. Nothing material is left to inference.

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?

Schema coverage is 100% and the schema already documents the null/omitted semantics, so the baseline is 3. The description earns a bump by telling the agent how to source the value (current chat's absolute project path) and which candidate path is wrong (the plugin installation directory), which is meaning the schema does not encode.

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 and resource: 'Open SpecPlanner for the current Codex project.' An agent can tell this is a panel-launching tool rather than a data read/write tool like read_board or create_change. It stops short of naming a sibling it should be preferred over, so it lands at 4 rather than 5.

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

Usage Guidelines4/5

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

Gives explicit do/don't guidance: pass the absolute project directory from chat context, do not ask for an environment variable, do not use the plugin installation directory, and omit workspacePath when no project directory exists. What it lacks is any routing against siblings (e.g., connect_workspace or workspace_info), so it is clear context without alternatives.

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