Skip to main content
Glama

start_planning

Initiate a software development planning session by defining a clear goal to generate actionable tasks and implementation plans.

Instructions

Start a new planning session with a goal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesThe software development goal to plan

Implementation Reference

  • Handler implementation for the 'start_planning' tool. Extracts the goal from arguments, creates a new goal and empty plan using storage, sets it as current goal, and returns the SEQUENTIAL_THINKING_PROMPT.
    case 'start_planning': {
      const { goal } = request.params.arguments as { goal: string };
      this.currentGoal = await storage.createGoal(goal);
      await storage.createPlan(this.currentGoal.id);
    
      return {
        content: [
          {
            type: 'text',
            text: SEQUENTIAL_THINKING_PROMPT,
          },
        ],
      };
    }
  • Input schema definition for the 'start_planning' tool, specifying an object with a required 'goal' string property.
    inputSchema: {
      type: 'object',
      properties: {
        goal: {
          type: 'string',
          description: 'The software development goal to plan',
        },
      },
      required: ['goal'],
    },
  • src/index.ts:114-126 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and input schema for 'start_planning'.
      name: 'start_planning',
      description: 'Start a new planning session with a goal',
      inputSchema: {
        type: 'object',
        properties: {
          goal: {
            type: 'string',
            description: 'The software development goal to plan',
          },
        },
        required: ['goal'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Start a new planning session' but doesn't explain what this entails—whether it creates a persistent session, requires authentication, has side effects, or what the expected outcome is. This is a significant gap for a tool that likely involves mutation.

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 description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the complexity of starting a planning session (likely a mutation with no output schema and no annotations), the description is incomplete. It lacks details on behavior, outcomes, or how it interacts with sibling tools, failing to provide sufficient context for effective use by an agent.

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?

The input schema has 100% description coverage, with the 'goal' parameter documented as 'The software development goal to plan'. The description adds no additional meaning beyond this, as it only mentions 'with a goal' without elaborating on format or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Start a new planning session') and the resource ('with a goal'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'save_plan' or 'add_todo', which might also involve planning-related actions, so it lacks specific sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'save_plan' or 'add_todo'. It implies usage for initiating planning but offers no context on prerequisites, exclusions, or specific scenarios, leaving the agent without clear direction.

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/NightTrek/Software-planning-mcp'

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