Skip to main content
Glama
PhilippMT

Software Planning Tool

by PhilippMT

start_planning

Initiate software development planning by defining a goal to generate structured tasks with complexity scoring and implementation guidance.

Instructions

Start a new planning session with a goal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesThe software development goal to plan

Implementation Reference

  • Handler for the 'start_planning' tool: parses the goal argument, creates a new goal and 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,
          },
        ],
      };
    }
  • src/index.ts:113-126 (registration)
    Registration of the 'start_planning' tool in the ListTools response, defining name, description, and input schema.
    {
      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'],
      },
    },
  • Input schema definition for the 'start_planning' tool, specifying the required 'goal' string parameter.
    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 the action ('Start a new planning session') but doesn't explain what this entails—such as whether it creates a persistent session, requires authentication, has side effects, or returns any data. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loaded with the core action and resource, making it easy to understand at a glance. Every part of the sentence earns its place by conveying essential information.

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 tool's complexity (initiating a session), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what happens after starting the session, what data is returned, or how it interacts with sibling tools like 'save_plan'. For a tool with these gaps, more context is needed to be fully helpful.

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 schema description coverage is 100%, so the schema already documents the single parameter 'goal' with its type and description. The description adds no additional meaning beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 verb ('Start') and resource ('a new planning session') with the specific purpose of establishing a goal. It distinguishes from siblings like 'add_todo' or 'save_plan' by focusing on session initiation rather than task management or persistence. However, it doesn't explicitly differentiate from potential overlapping tools, keeping it at a 4 instead of 5.

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', nor does it mention prerequisites or context for starting a planning session. It lacks explicit when/when-not instructions or named alternatives, leaving usage unclear beyond the basic purpose.

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

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