Skip to main content
Glama
rwese
by rwese

todo-read

Retrieve and filter backlog todos by status or batch to track work item progress and dependencies.

Instructions

Read-only access to backlog todos - list and filter todos for a backlog item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic name (required)
statusNoFilter by status
batchNoFilter by batch

Implementation Reference

  • The primary handler function for the "todo-read" MCP tool. It validates input, constructs filters, calls listTodos helper, and returns JSON serialized todos.
    async function handleBacklogTodoRead(args: any) {
      const { topic, status, batch } = args;
      if (!topic) throw new Error("topic is required");
    
      const filters: any = {};
      if (status) filters.status = status;
      if (batch) filters.batch = batch;
    
      const todos = listTodos(topic, filters);
      return JSON.stringify(todos, null, 2);
    }
  • Input schema definition for the "todo-read" tool, defining required 'topic' and optional 'status'/'batch' filters.
      name: "todo-read",
      description: "Read-only access to backlog todos - list and filter todos for a backlog item",
      inputSchema: {
        type: "object",
        properties: {
          topic: {
            type: "string",
            description: "Topic name (required)",
          },
          status: {
            type: "string",
            enum: ["pending", "in_progress", "completed", "cancelled"],
            description: "Filter by status",
          },
          batch: {
            type: "string",
            description: "Filter by batch",
          },
        },
        required: ["topic"],
      },
    },
  • src/index.ts:720-742 (registration)
    Tool registration entry in the ListTools response, which exposes the "todo-read" tool to MCP clients with its schema.
    {
      name: "todo-read",
      description: "Read-only access to backlog todos - list and filter todos for a backlog item",
      inputSchema: {
        type: "object",
        properties: {
          topic: {
            type: "string",
            description: "Topic name (required)",
          },
          status: {
            type: "string",
            enum: ["pending", "in_progress", "completed", "cancelled"],
            description: "Filter by status",
          },
          batch: {
            type: "string",
            description: "Filter by batch",
          },
        },
        required: ["topic"],
      },
    },
  • Key helper function implementing todo listing and filtering logic by reading from todos.json and applying optional status and batch filters.
    export function listTodos(topic: string, filters?: { status?: string, batch?: string }): Todo[] {
      const data = readTodos(topic);
      let todos = data.todos;
    
      if (filters?.status) {
        todos = todos.filter(t => t.status === filters.status);
      }
    
      if (filters?.batch) {
        todos = todos.filter(t => t.batch === filters.batch);
      }
    
      return todos;
    }
  • Helper function to read todos data from the JSON file for a given backlog topic, returning empty list if file missing.
    export function readTodos(topic: string): TodoData {
      const filePath = getTodosFilePath(topic);
      try {
        const content = readFileSync(filePath, 'utf8');
        return JSON.parse(content);
      } catch (error) {
        // File doesn't exist or is invalid, return empty structure
        return { backlogTopic: topic, todos: [] };
      }
    }
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 'read-only access', which implies non-destructive behavior, but doesn't cover other aspects like authentication needs, rate limits, error handling, or return format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operational 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 that front-loads key information ('read-only access', 'list and filter todos'). Every word contributes to understanding the tool's purpose without redundancy or unnecessary elaboration.

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 no annotations, no output schema, and a tool that performs read operations with filtering, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, pagination), error conditions, or how it differs from similar tools. This leaves the agent with insufficient context for reliable use.

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 description mentions 'filter todos' but doesn't elaborate on parameters beyond what the schema provides. With 100% schema description coverage, the schema already documents all three parameters (topic, status, batch) clearly, including required status and enum values. The description adds no additional semantic context, so it 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 tool's purpose as 'list and filter todos for a backlog item' with 'read-only access to backlog todos', providing a specific verb ('list and filter') and resource ('todos for a backlog item'). However, it doesn't explicitly differentiate from sibling tools like 'read' or 'todo-done', which could have overlapping functionality.

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 like 'read', 'todo-done', or 'todo-write'. It mentions 'read-only access' but doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer usage from the name and purpose alone.

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