Skip to main content
Glama
rwese
by rwese

todo-write

Create and update backlog todos to manage work items with status tracking, dependencies, and versioning.

Instructions

Write access to backlog todos - create and update todos for backlog items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform
topicYesTopic name (required)
todoIdNoTodo ID (required for update)
contentNoTodo content
statusNoTodo status
dependenciesNoTodo dependencies (array of todo IDs)
batchNoBatch identifier

Implementation Reference

  • Primary handler function executing the todo-write tool logic, handling create, update, and list actions for backlog todos using shared utilities.
    async function handleBacklogTodoWrite(args: any) {
      const { action, topic, todoId, content, status, dependencies, batch } = args;
      if (!topic) throw new Error("topic is required");
    
      switch (action) {
        case "create": {
          if (!content) throw new Error("content is required for create action");
          
          const data = readTodos(topic);
          const newTodo = {
            id: crypto.randomUUID(),
            content,
            status: status || "pending",
            dependencies: dependencies || [],
            batch: batch || null,
            created: new Date().toISOString(),
            agent: "mcp-backlog",
            session: crypto.randomUUID(),
          };
          
          data.todos.push(newTodo);
          writeTodos(topic, data);
          return `Created todo: ${newTodo.id}`;
        }
    
        case "update": {
          if (!todoId) throw new Error("todoId is required for update action");
          
          const data = readTodos(topic);
          const todo = data.todos.find(t => t.id === todoId);
          if (!todo) throw new Error(`Todo not found: ${todoId}`);
          
          if (content !== undefined) todo.content = content;
          if (status !== undefined) todo.status = status as any;
          if (dependencies !== undefined) todo.dependencies = dependencies;
          if (batch !== undefined) todo.batch = batch;
          
          writeTodos(topic, data);
          return `Updated todo: ${todoId}`;
        }
    
        case "list": {
          return await handleBacklogTodoRead({ topic, status, batch });
        }
    
        default:
          throw new Error(`Unknown action: ${action}`);
      }
    }
  • Input schema defining parameters and validation for the todo-write tool.
    inputSchema: {
      type: "object",
      properties: {
        action: {
          type: "string",
          enum: ["create", "update", "list"],
          description: "Operation to perform",
        },
        topic: {
          type: "string",
          description: "Topic name (required)",
        },
        todoId: {
          type: "string",
          description: "Todo ID (required for update)",
        },
        content: {
          type: "string",
          description: "Todo content",
        },
        status: {
          type: "string",
          enum: ["pending", "in_progress", "completed", "cancelled"],
          description: "Todo status",
        },
        dependencies: {
          type: "array",
          items: { type: "string" },
          description: "Todo dependencies (array of todo IDs)",
        },
        batch: {
          type: "string",
          description: "Batch identifier",
        },
      },
      required: ["action", "topic"],
    },
  • src/index.ts:743-783 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and schema.
    {
      name: "todo-write",
      description: "Write access to backlog todos - create and update todos for backlog items",
      inputSchema: {
        type: "object",
        properties: {
          action: {
            type: "string",
            enum: ["create", "update", "list"],
            description: "Operation to perform",
          },
          topic: {
            type: "string",
            description: "Topic name (required)",
          },
          todoId: {
            type: "string",
            description: "Todo ID (required for update)",
          },
          content: {
            type: "string",
            description: "Todo content",
          },
          status: {
            type: "string",
            enum: ["pending", "in_progress", "completed", "cancelled"],
            description: "Todo status",
          },
          dependencies: {
            type: "array",
            items: { type: "string" },
            description: "Todo dependencies (array of todo IDs)",
          },
          batch: {
            type: "string",
            description: "Batch identifier",
          },
        },
        required: ["action", "topic"],
      },
    },
  • src/index.ts:840-845 (registration)
    Dispatch registration for todo-write tool in the CallToolRequestSchema switch statement.
    case "todo-write":
      result = await handleBacklogTodoWrite(request.params.arguments);
      break;
    case "todo-done":
      result = await handleBacklogTodoDone(request.params.arguments);
      break;
  • Import of helper functions from backlog-todo-shared.js used by the todo-write handler for reading/writing todos.
      readTodos,
      writeTodos,
      listTodos,
      validateDependencies
    } from '../lib/backlog-todo-shared.js';
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 mentions 'write access' and operations like 'create and update', implying mutation, but fails to detail permissions, side effects, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded in a single sentence: 'Write access to backlog todos - create and update todos for backlog items.' It wastes no words and directly states the core functionality. However, it could be slightly more structured by explicitly separating purpose from scope.

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 (7 parameters, mutation operations) and lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions or side effects, nor does it explain return values. For a tool with 'create' and 'update' actions, more context is needed to ensure safe and correct usage.

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%, so the schema already documents all 7 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't explain 'topic' or 'batch' further). With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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 tool's purpose: 'Write access to backlog todos - create and update todos for backlog items.' It specifies the verb ('create and update') and resource ('backlog todos'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'write' (which might be similar) or 'todo-done' (which handles completion), so it lacks sibling differentiation.

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 when to choose 'todo-write' over 'write' or 'todo-done', nor does it specify prerequisites or exclusions. The only implied usage is for backlog todos, but this is too vague for effective 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/rwese/mcp-backlog'

If you have feedback or need assistance with the MCP directory API, please join our Discord server