Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

get_logs

Retrieve log entries for specific plan nodes to track progress, reasoning, decisions, challenges, and comments during project planning.

Instructions

Get log entries for a node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
node_idYesNode ID
log_typeNoFilter by log type
limitNoMaximum number of logs to return

Implementation Reference

  • Executes the get_logs tool: parses input arguments, retrieves logs using apiClient, applies optional log_type filter and limit, formats and returns the response.
    if (name === "get_logs") {
      const { plan_id, node_id, log_type, limit = 50 } = args;
      
      let logs = await apiClient.logs.getLogs(plan_id, node_id);
      
      // Apply filters
      if (log_type) {
        logs = logs.filter(log => log.log_type === log_type);
      }
      
      // Apply limit
      logs = logs.slice(0, limit);
      
      return formatResponse(logs);
    }
  • Input schema defining parameters for the get_logs tool: plan_id and node_id (required), optional log_type filter and limit.
    inputSchema: {
      type: "object",
      properties: {
        plan_id: { type: "string", description: "Plan ID" },
        node_id: { type: "string", description: "Node ID" },
        log_type: { 
          type: "string", 
          description: "Filter by log type",
          enum: ["progress", "reasoning", "challenge", "decision", "comment"]
        },
        limit: {
          type: "integer",
          description: "Maximum number of logs to return",
          default: 50
        }
      },
      required: ["plan_id", "node_id"]
    }
  • src/tools.js:300-321 (registration)
    Tool registration in the ListTools response array, including name, description, and schema.
    {
      name: "get_logs",
      description: "Get log entries for a node",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          node_id: { type: "string", description: "Node ID" },
          log_type: { 
            type: "string", 
            description: "Filter by log type",
            enum: ["progress", "reasoning", "challenge", "decision", "comment"]
          },
          limit: {
            type: "integer",
            description: "Maximum number of logs to return",
            default: 50
          }
        },
        required: ["plan_id", "node_id"]
      }
    },
  • Helper function in apiClient.logs that performs the HTTP GET request to retrieve logs from the backend API.
    getLogs: async (planId, nodeId) => {
      const response = await apiClient.get(`/plans/${planId}/nodes/${nodeId}/logs`);
      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 the full burden but only states the basic action without disclosing behavioral traits. It doesn't cover whether this is a read-only operation, potential rate limits, authentication needs, error conditions, or what the return format looks like (e.g., pagination, structure). This is a significant gap for a tool with multiple parameters and no output schema.

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 with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly, which is ideal for conciseness.

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 complexity (4 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return values, error handling, or behavioral context, leaving gaps that could hinder an AI agent's ability to use the tool effectively. The high schema coverage helps with parameters but doesn't compensate for other missing details.

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 input schema has 100% description coverage, so parameters like 'plan_id', 'node_id', 'log_type', and 'limit' are well-documented in the schema. The description adds no additional meaning beyond implying filtering by node, which is already covered by the 'node_id' parameter. 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') and resource ('log entries for a node'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_node_context' or 'get_plan_summary', which might also retrieve related information but focus on different aspects of nodes or plans.

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 and node), exclusions, or compare it to siblings like 'search' or 'get_node_ancestry', leaving the agent without context for tool selection.

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