Skip to main content
Glama

Knowledge MCP Server

by sven-borkert

get_next_todo_task

Retrieve the next incomplete task from a TODO list for sequential execution. Use this tool to identify pending tasks, continue interrupted work, or follow task order efficiently while managing projects.

Instructions

Get the next incomplete task in a TODO list for sequential execution.

When to use this tool:

  • Working through TODO sequentially
  • Finding next task to implement
  • Checking for remaining work
  • Continuing interrupted work
  • Following task order

Key features:

  • Returns first incomplete task
  • Provides task number and description
  • Indicates when all complete
  • Maintains task sequence

You should:

  1. Use after completing current task
  2. Follow sequential task order
  3. Handle "all complete" case
  4. Read full task details if needed
  5. Mark complete before getting next

DO NOT use when:

  • Need specific task (not next)
  • Want full TODO overview
  • All tasks already complete

Returns: {success: bool, task?: {number: int, description: str}, message?: str, error?: str}

Input Schema

NameRequiredDescriptionDefault
project_idYesThe project identifier
todo_numberYesThe TODO list number

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "project_id": { "description": "The project identifier", "maxLength": 100, "minLength": 1, "type": "string" }, "todo_number": { "description": "The TODO list number", "exclusiveMinimum": 0, "maximum": 99999, "type": "integer" } }, "required": [ "project_id", "todo_number" ], "type": "object" }

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/sven-borkert/knowledge-mcp'

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