Skip to main content
Glama

open_work_plan

Open an interactive task tree, dependency graph, and notes board to manage multi-day engineering projects; optionally focus on a specific project.

Instructions

Open the interactive Work Plan task tree, dependency graph, and notes board.

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_work_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoOptional project ID to focus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it says nothing about what "open" actually does: whether it returns UI state, mutates the client session, requires a UI-capable client, or fails outside one. "Interactive" hints at a UI surface but no side effects, preconditions, or return behavior are disclosed.

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?

One front-loaded sentence with no filler, and the three UI surfaces are enumerated efficiently. It is arguably too terse for a tool with no annotations, but nothing in it is wasted.

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

Completeness2/5

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

For a zero-annotation, no-output-schema UI launch tool, the description should explain what opening returns and any client requirements or preconditions. It leaves out everything except the names of the surfaces shown, which is not enough for an agent to invoke it confidently.

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

Parameters3/5

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

Schema description coverage is 100% for the single optional project_id parameter, so the schema already documents it as an optional focus target. The description adds no meaning beyond that, which is acceptable given the high coverage but not above baseline.

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?

The description uses a specific verb ("Open") and names the concrete resource being opened: the Work Plan task tree, dependency graph, and notes board. That is much clearer than a tautology, but it offers no differentiation from UI siblings such as ui_get_state or ui_select_project, so an agent cannot tell which entry point to choose.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus alternatives like task_plan, ui_get_state, or ui_select_project. Usage is only implied by the word "Open", leaving the agent to guess the context in which this UI launch is appropriate.

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