Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

create_node

Add phases, tasks, or milestones to hierarchical project plans. Specify parent relationships, status, due dates, and completion criteria to structure project planning.

Instructions

Create a new node in a plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
parent_idNoParent node ID (optional, defaults to root)
node_typeYesNode type
titleYesNode title
descriptionNoNode description
statusNoNode statusnot_started
contextNoAdditional context for the node
agent_instructionsNoInstructions for AI agents working on this node
acceptance_criteriaNoCriteria for node completion
due_dateNoDue date (ISO format)
metadataNoAdditional metadata

Implementation Reference

  • Handler for the create_node MCP tool. Destructures plan_id from arguments, passes remaining nodeData to apiClient.nodes.createNode, and formats the response using formatResponse.
    if (name === "create_node") {
      const { plan_id, ...nodeData } = args;
      const result = await apiClient.nodes.createNode(plan_id, nodeData);
      return formatResponse(result);
    }
  • Input schema definition for create_node tool, specifying properties, types, enums, descriptions, and required fields.
    inputSchema: {
      type: "object",
      properties: {
        plan_id: { type: "string", description: "Plan ID" },
        parent_id: { type: "string", description: "Parent node ID (optional, defaults to root)" },
        node_type: { 
          type: "string", 
          description: "Node type",
          enum: ["phase", "task", "milestone"]
        },
        title: { type: "string", description: "Node title" },
        description: { type: "string", description: "Node description" },
        status: { 
          type: "string", 
          description: "Node status",
          enum: ["not_started", "in_progress", "completed", "blocked"],
          default: "not_started"
        },
        context: { type: "string", description: "Additional context for the node" },
        agent_instructions: { type: "string", description: "Instructions for AI agents working on this node" },
        acceptance_criteria: { type: "string", description: "Criteria for node completion" },
        due_date: { type: "string", description: "Due date (ISO format)" },
        metadata: { type: "object", description: "Additional metadata" }
      },
      required: ["plan_id", "node_type", "title"]
  • src/tools.js:170-199 (registration)
    Tool registration in the MCP tools list returned by ListToolsRequestSchema handler, including name, description, and inputSchema.
    {
      name: "create_node",
      description: "Create a new node in a plan",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          parent_id: { type: "string", description: "Parent node ID (optional, defaults to root)" },
          node_type: { 
            type: "string", 
            description: "Node type",
            enum: ["phase", "task", "milestone"]
          },
          title: { type: "string", description: "Node title" },
          description: { type: "string", description: "Node description" },
          status: { 
            type: "string", 
            description: "Node status",
            enum: ["not_started", "in_progress", "completed", "blocked"],
            default: "not_started"
          },
          context: { type: "string", description: "Additional context for the node" },
          agent_instructions: { type: "string", description: "Instructions for AI agents working on this node" },
          acceptance_criteria: { type: "string", description: "Criteria for node completion" },
          due_date: { type: "string", description: "Due date (ISO format)" },
          metadata: { type: "object", description: "Additional metadata" }
        },
        required: ["plan_id", "node_type", "title"]
      }
    },
  • Helper function in apiClient.nodes that makes the HTTP POST request to create the node via the backend API.
    createNode: async (planId, nodeData) => {
      const response = await apiClient.post(`/plans/${planId}/nodes`, nodeData);
      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. While 'Create' implies a write/mutation operation, the description doesn't address permission requirements, whether creation is idempotent, what happens on failure, or what the response contains. For a creation tool with 11 parameters, this leaves significant behavioral unknowns.

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 states the core purpose without unnecessary elaboration. It's appropriately sized for a tool with comprehensive schema documentation and gets straight to the point with zero wasted words.

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 creation tool with 11 parameters and no annotations or output schema, the description is insufficient. It doesn't explain what happens after creation, what the return value contains, error conditions, or how this tool relates to the broader plan/node management system. The context signals indicate significant complexity that the description doesn't address.

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%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond the schema's comprehensive documentation. This meets the baseline expectation when schema coverage is complete.

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 ('Create a new node') and resource ('in a plan'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_plan' or 'update_node', which would require more specificity about what makes node creation distinct.

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 'create_plan' (for creating the plan itself) or 'update_node' (for modifying existing nodes). There's no mention of prerequisites, dependencies, or contextual factors that would help an agent choose appropriately among sibling tools.

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