Skip to main content
Glama

list_tasks

View all tasks in your task management system to track progress and organize your workflow.

Instructions

List all tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the list_tasks tool, which formats and returns the list of current tasks.
    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
            )
        ]
  • The registration of the list_tasks tool within the MCP server's list_tools handler.
    types.Tool(
        name="list_tasks",
        description="List all tasks",
        inputSchema={
            "type": "object",
            "properties": {}
        }
    ),
Behavior1/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 fails to indicate read-only safety, pagination behavior, return format, or scope constraints. The description provides zero behavioral context beyond the tool name.

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

Conciseness2/5

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

While brief (3 words), the description suffers from under-specification rather than effective conciseness. The single sentence fails to earn its place by adding value beyond the tool name, and lacks front-loaded critical context about behavioral safety.

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?

With no output schema, no annotations, and mutation-capable siblings, the description inadequately prepares the agent for tool selection. It omits critical context that this is a safe read operation and lacks any scope clarification necessary for an unparameterized list operation.

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?

Input schema contains zero parameters. Per rubric guidelines, 0 params establishes a baseline score of 4, as there are no parameter semantics to describe.

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

Purpose2/5

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

The description 'List all tasks' restates the tool name (tautology). While it confirms the action and resource, it fails to distinguish from siblings (add_task, complete_task, delete_task) or clarify scope (e.g., user-specific vs global tasks).

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?

No guidance provided on when to use this tool versus mutation alternatives (add_task, complete_task, delete_task). No mention of prerequisites or filtering limitations despite the 'all' scope implication.

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/devirokkam/MCP_Github_Deployment'

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