Skip to main content
Glama

planner

Read-only

Breaks down complex tasks into interactive, sequential plans with revision and branching for project planning, system design, and architectural decisions.

Instructions

Breaks down complex tasks through interactive, sequential planning with revision and branching capabilities. Use for complex project planning, system design, migration strategies, and architectural decisions. Builds plans incrementally with deep reflection for complex scenarios.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepYesPlanning content for this step. Step 1: describe the task, problem and scope. Later steps: capture updates, revisions, branches, or open questions that shape the plan.
modelYesCurrently in auto model selection mode. CRITICAL: When the user names a model, you MUST use that exact name unless the server rejects it. If no model is provided, you may use the `listmodels` tool to review options and select an appropriate match. Top models: gemini-2.5-pro (score 100, 1.0M ctx, thinking, code-gen); gemini-3-pro-preview (score 100, 1.0M ctx, thinking, code-gen); gemini-2.5-flash (score 61, 1.0M ctx, thinking); gemini-2.0-flash (score 56, 1.0M ctx, thinking); gemini-2.0-flash-lite (score 42, 1.0M ctx).
branch_idNoName for this branch (e.g. 'approach-A', 'migration-path').
step_numberYesCurrent step number in work sequence (starts at 1)
total_stepsYesEstimated total steps needed to complete work
continuation_idNoUnique thread continuation ID for multi-turn conversations. Works across different tools. ALWAYS reuse the last continuation_id you were given—this preserves full conversation context, files, and findings so the agent can resume seamlessly.
is_branch_pointNoTrue when this step creates a new branch to explore an alternative path.
branch_from_stepNoIf branching, the step number that this branch starts from.
is_step_revisionNoSet true when you are replacing a previously recorded step.
more_steps_neededNoTrue when you now expect to add additional steps beyond the prior estimate.
next_step_requiredYesWhether another work step is needed. When false, aim to reduce total_steps to match step_number to avoid mismatch.
revises_step_numberNoStep number being replaced when revising.
use_assistant_modelNoUse assistant model for expert analysis after workflow steps. False skips expert analysis, relies solely on your personal investigation. Defaults to True for comprehensive validation.
Behavior2/5

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

Description says 'builds plans' implying modification, but annotation readOnlyHint=true suggests no side effects. This contradiction reduces transparency. Lacks details on plan storage, duration, or output format.

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 sentences, front-loaded with purpose and capabilities. Efficient but could be structured with bullet points for clarity.

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?

With 13 parameters and no output schema, the description lacks sufficient guidance on how to use the tool effectively, such as step flow or interaction model.

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 covers 100% of parameters with descriptions, so baseline is 3. Tool description briefly mentions revision and branching, but does not add significant meaning beyond the 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?

Tool name 'planner' and description clearly state it breaks down complex tasks for planning, system design, etc., distinguishing it from sibling tools like analyze, chat, or testgen.

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?

Explicitly recommends use for complex project planning, system design, migration strategies, and architectural decisions. Does not explicitly state when to avoid or name alternatives, but context signals and sibling list imply other tools for simpler tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bigl34/pal-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server