Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

add_log

Add structured log entries to planning nodes to document progress, reasoning, challenges, decisions, or comments, replacing traditional comment systems.

Instructions

Add a log entry to a node (replaces comments)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
node_idYesNode ID
contentYesLog content
log_typeNoType of log entrycomment
tagsNoTags for categorizing the log entry

Implementation Reference

  • Handler logic for the 'add_log' MCP tool. Destructures input arguments, prepares logData, calls apiClient.logs.addLogEntry, and formats the response.
    if (name === "add_log") {
      const { plan_id, node_id, content, log_type = "comment", tags } = args;
      
      const logData = {
        content,
        log_type,
        tags
      };
      
      const result = await apiClient.logs.addLogEntry(plan_id, node_id, logData);
      return formatResponse(result);
    }
  • Input schema definition for the 'add_log' tool, defining parameters like plan_id, node_id, content, log_type, and tags.
      name: "add_log",
      description: "Add a log entry to a node (replaces comments)",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          node_id: { type: "string", description: "Node ID" },
          content: { type: "string", description: "Log content" },
          log_type: { 
            type: "string", 
            description: "Type of log entry",
            enum: ["progress", "reasoning", "challenge", "decision", "comment"],
            default: "comment"
          },
          tags: { 
            type: "array", 
            description: "Tags for categorizing the log entry",
            items: { type: "string" }
          }
        },
        required: ["plan_id", "node_id", "content"]
      }
    },
  • src/tools.js:276-299 (registration)
    Registration of the 'add_log' tool in the ListToolsRequestSchema handler's tools array.
    {
      name: "add_log",
      description: "Add a log entry to a node (replaces comments)",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          node_id: { type: "string", description: "Node ID" },
          content: { type: "string", description: "Log content" },
          log_type: { 
            type: "string", 
            description: "Type of log entry",
            enum: ["progress", "reasoning", "challenge", "decision", "comment"],
            default: "comment"
          },
          tags: { 
            type: "array", 
            description: "Tags for categorizing the log entry",
            items: { type: "string" }
          }
        },
        required: ["plan_id", "node_id", "content"]
      }
    },
  • Helper function in api-client.js that executes the actual HTTP POST request to add a log entry to the backend API.
    addLogEntry: async (planId, nodeId, logData) => {
      const response = await apiClient.post(`/plans/${planId}/nodes/${nodeId}/log`, logData);
      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 of behavioral disclosure. It states 'Add a log entry' (implies mutation) and 'replaces comments', hinting at destructive behavior, but doesn't clarify permissions, side effects, or response format. This is inadequate for a mutation tool with zero annotation coverage, leaving significant gaps in understanding its behavior.

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 zero waste. It's front-loaded with the core action and includes a clarifying note ('replaces comments') that adds value without verbosity. Every word earns its place, making it highly concise and well-structured.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on permissions, side effects, return values, and how it fits into the broader toolset. The mention of 'replaces comments' is vague and doesn't fully address behavioral context, leaving the agent under-informed.

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 the schema fully documents all 5 parameters. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or usage examples. Baseline 3 is appropriate as the schema handles the heavy lifting, but the description doesn't compensate or enhance parameter understanding.

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 verb 'Add' and resource 'log entry to a node', making the purpose specific and understandable. It distinguishes from siblings like 'get_logs' (read) and 'update_node' (general update). However, it doesn't explicitly differentiate from potential overlapping tools like 'update_node' for log-related updates, keeping it from 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. It mentions 'replaces comments' but doesn't explain what that means in context or when to choose this over other tools like 'update_node' for logging. No explicit when/when-not or alternative tool references are included.

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