Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

get_node_ancestry

Retrieve the complete hierarchical path from root to a specific node in a planning system to understand its position and relationships within the structure.

Instructions

Get the path from root to a specific node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
node_idYesNode ID

Implementation Reference

  • Handler function that destructures plan_id and node_id from arguments and makes an API GET request to retrieve the ancestry path for the specified node.
    if (name === "get_node_ancestry") {
      const { plan_id, node_id } = args;
      
      // Get node ancestry
      const response = await apiClient.axiosInstance.get(
        `/plans/${plan_id}/nodes/${node_id}/ancestry`
      );
      
      return formatResponse(response.data);
    }
  • src/tools.js:262-273 (registration)
    Tool registration including name, description, and input schema specification for the get_node_ancestry tool.
    {
      name: "get_node_ancestry",
      description: "Get the path from root to a specific node",
      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 full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns structured data, or handles errors. For a tool with no 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 directly states the tool's purpose without unnecessary words. It's appropriately front-loaded with the core functionality, making it easy to parse quickly.

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 (retrieving hierarchical data), lack of annotations, and no output schema, the description is minimally adequate. It clarifies the retrieval scope but doesn't address authentication needs, return format, or error handling, leaving room for improvement in completeness.

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%, with both parameters clearly documented in the schema. The description adds no additional parameter semantics beyond implying that 'node_id' identifies the target node and 'plan_id' provides context, which the schema already covers. This meets the baseline for high schema coverage.

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 the path from root to') and resource ('a specific node'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_node_context' or 'get_plan_structure' that might also retrieve node-related information, preventing a perfect score.

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. With siblings like 'get_node_context' and 'get_plan_structure' that likely retrieve related node or plan data, there's no indication of when this ancestry-specific retrieval is preferred, leaving usage context unclear.

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