Skip to main content
Glama

get_todos

Retrieve all tasks in the current software development plan to track progress and manage implementation details.

Instructions

Get all todos in the current plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'get_todos' tool in the MCP server. It checks if a current goal exists, fetches the todos using storage.getTodos, and returns them serialized as JSON.
    case 'get_todos': {
      if (!this.currentGoal) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'No active goal. Start a new planning session first.'
        );
      }
    
      const todos = await storage.getTodos(this.currentGoal.id);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(todos, null, 2),
          },
        ],
      };
    }
  • src/index.ts:183-190 (registration)
    Registration of the 'get_todos' tool in the list of available tools, including its name, description, and input schema (empty object).
    {
      name: 'get_todos',
      description: 'Get all todos in the current plan',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the 'get_todos' tool, which requires no parameters (empty properties).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Helper function in storage that retrieves the list of todos for a specific goal from the implementation plan.
    async getTodos(goalId: string): Promise<Todo[]> {
      const plan = await this.getPlan(goalId);
      return plan?.todos || [];
    }
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. It states 'Get all todos' but doesn't disclose behavioral traits like whether this returns a list, pagination details, error conditions, or if it requires specific permissions. The description is minimal and lacks essential operational context for a read tool.

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 action and resource, making it easy to parse quickly. Every part of the sentence contributes to understanding the tool's purpose.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'Get' returns (e.g., a list of todos, their structure, or any metadata), nor does it cover behavioral aspects like error handling. For a tool with no structured data support, this leaves significant gaps in understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description implies no inputs are required, which aligns with the schema. Baseline is 4 for zero parameters, as no additional semantic explanation is needed.

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 ('all todos in the current plan'), making the purpose understandable. It doesn't explicitly differentiate from siblings like 'update_todo_status' or 'remove_todo', but the verb 'Get' implies a read operation versus mutations, providing some implicit distinction.

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 explicit guidance on when to use this tool versus alternatives. It mentions 'current plan' but doesn't clarify prerequisites, such as whether a plan must be active or if this works with any plan state. No exclusions or comparisons to siblings are stated.

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/NightTrek/Software-planning-mcp'

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