Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

create_plan

Create structured project plans with phases, tasks, and milestones. Define plan title, description, and status to organize hierarchical planning for AI agents.

Instructions

Create a new plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPlan title
descriptionNoPlan description
statusNoPlan statusdraft

Implementation Reference

  • MCP tool handler for 'create_plan': dispatches to apiClient.plans.createPlan with input arguments and formats the response using formatResponse.
    if (name === "create_plan") {
      const result = await apiClient.plans.createPlan(args);
      return formatResponse(result);
    }
  • Input schema for the 'create_plan' tool defining parameters: title (required), description, status.
    inputSchema: {
      type: "object",
      properties: {
        title: { type: "string", description: "Plan title" },
        description: { type: "string", description: "Plan description" },
        status: { 
          type: "string", 
          description: "Plan status",
          enum: ["draft", "active", "completed", "archived"],
          default: "draft"
        }
      },
      required: ["title"]
    }
  • src/tools.js:122-138 (registration)
    Tool registration object for 'create_plan' in the ListTools response, including name, description, and inputSchema.
      name: "create_plan",
      description: "Create a new plan",
      inputSchema: {
        type: "object",
        properties: {
          title: { type: "string", description: "Plan title" },
          description: { type: "string", description: "Plan description" },
          status: { 
            type: "string", 
            description: "Plan status",
            enum: ["draft", "active", "completed", "archived"],
            default: "draft"
          }
        },
        required: ["title"]
      }
    },
  • Helper function in API client that performs HTTP POST to '/plans' endpoint to create a new plan.
    createPlan: async (planData) => {
      const response = await apiClient.post('/plans', planData);
      return response.data;
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a new plan' implies a write/mutation operation, but doesn't disclose any behavioral traits like required permissions, whether creation is idempotent, what happens on duplicate titles, or what the response contains. For a mutation tool with zero annotation coverage, this is inadequate.

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 maximally concise with just three words. It's front-loaded with the essential action and resource. There's zero waste or unnecessary elaboration, making it efficient for scanning and comprehension.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a 'plan' in this system, what happens after creation, or how this tool relates to other plan management tools. The agent would need to guess about the tool's behavior and integration with the broader system.

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 description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for all three parameters (title, description, status). The baseline is 3 since the schema does the heavy lifting, but the description doesn't compensate by explaining relationships between parameters or providing usage examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new plan' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'create' and resource 'plan', but doesn't distinguish this from sibling tools like 'create_node' or explain what a 'plan' represents in this system. The purpose is clear at a basic level but lacks differentiation from alternatives.

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

Usage Guidelines1/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. There are multiple sibling tools that interact with plans (delete_plan, get_plan_structure, get_plan_summary, list_plans, update_plan), but the description offers no context about when creation is appropriate versus updating existing plans or retrieving plan information.

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/TAgents/agent-planner-mcp'

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