Skip to main content
Glama
gvbigdata

Task MCP Server

by gvbigdata
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python

list_tasks

Retrieve all tasks from the task management server to view current items and track progress.

Instructions

List all tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/task_mcp_server/server.py:100-121 (handler)
    Executes the list_tasks tool by checking if tasks exist, formatting a markdown list of all tasks with status indicators, and returning as TextContent.
    elif name == "list_tasks":
    if not tasks:
        return [
            types.TextContent(
                type="text",
                text="No tasks found. Add a task to get started!"
            )
        ]
    
    task_list = "📋 Task List:\n\n"
    for task_id, task in tasks.items():
        status = "✓" if task["completed"] else "○"
        task_list += f"{status} [{task_id}] {task['title']}\n"
        if task["description"]:
            task_list += f"   └─ {task['description']}\n"
    
    return [
        types.TextContent(
            type="text",
            text=task_list
        )
    ]
  • src/task_mcp_server/server.py:36-43 (registration)
    Registers the list_tasks tool in the @server.list_tools() handler, including name, description, and empty input schema.
    types.Tool(
    name="list_tasks",
    description="List all tasks",
    inputSchema={
        "type": "object",
        "properties": {}
    }
),
  • src/task_mcp_server/server.py:39-42 (schema)
    Input schema for list_tasks tool: no required properties.
    inputSchema={
    "type": "object",
    "properties": {}
}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It indicates a read-only list operation, but does not mention output format, pagination, ordering, or whether deleted tasks are included. No contradiction with annotations exists.

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 two words and completely free of filler. It is front-loaded and every word adds meaning, making it appropriate for such a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (no parameters, no output schema), the description is minimally adequate. However, it does not disclose return value structure or any edge-case behavior, which would be helpful for a complete contextual picture.

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 zero parameters and full schema coverage, so the description does not need to explain parameters. The baseline for 0-parameter tools is 4, and the description does not detract from this.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all tasks' clearly states the action (list) and resource (tasks), with 'all' specifying scope. It distinguishes itself from task-related sibling tools like create_task, update_task, and delete_task.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the tool name and sibling context: it is for retrieving tasks. However, the description offers no explicit 'when to use' or 'alternatives' guidance, leaving the agent to infer from the name 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