Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

get_node_context

Retrieve comprehensive context for planning nodes including children, logs, and artifacts to support structured project planning and decision-making.

Instructions

Get comprehensive context for a node including children, logs, and artifacts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
node_idYesNode ID

Implementation Reference

  • The handler function for the 'get_node_context' MCP tool. It extracts plan_id and node_id from arguments and makes an API call to retrieve the node's comprehensive context (including children, logs, and artifacts) from the backend endpoint `/plans/{plan_id}/nodes/{node_id}/context`, then formats the response.
    if (name === "get_node_context") {
      const { plan_id, node_id } = args;
      
      // Get node with context
      const response = await apiClient.axiosInstance.get(
        `/plans/${plan_id}/nodes/${node_id}/context`
      );
      
      return formatResponse(response.data);
    }
  • src/tools.js:250-261 (registration)
    Registration of the 'get_node_context' tool in the ListToolsRequestHandler response. Includes the tool name, description, and input schema definition.
    {
      name: "get_node_context",
      description: "Get comprehensive context for a node including children, logs, and artifacts",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          node_id: { type: "string", description: "Node ID" }
        },
        required: ["plan_id", "node_id"]
      }
    },
  • Input schema for the 'get_node_context' tool, defining required plan_id and node_id parameters.
    inputSchema: {
      type: "object",
      properties: {
        plan_id: { type: "string", description: "Plan ID" },
        node_id: { type: "string", description: "Node ID" }
      },
      required: ["plan_id", "node_id"]
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves information ('Get'), implying a read-only operation, but doesn't specify permissions required, rate limits, pagination, or what 'comprehensive context' entails beyond the listed components. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 front-loads the key action and components. It avoids redundancy and wastes no words, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 required parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and scope but lacks details on behavioral traits, usage context, and output format. Without annotations or output schema, more guidance would be helpful, but it meets a basic threshold for a read operation.

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%, with both parameters ('plan_id' and 'node_id') documented in the schema. The description adds no parameter-specific details beyond what the schema provides, such as format examples or relationships between parameters. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 ('Get') and the target resource ('comprehensive context for a node'), specifying what information is included ('children, logs, and artifacts'). It distinguishes from siblings like 'get_node_ancestry' (which focuses on ancestry) and 'get_plan_structure' (which focuses on structure), but doesn't explicitly name these alternatives. The purpose is specific and actionable.

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. It doesn't mention prerequisites (e.g., needing a plan_id and node_id), exclusions, or comparisons to siblings like 'get_node_ancestry' or 'get_logs'. Usage is implied by the action but lacks explicit context or decision criteria.

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