Skip to main content
Glama
brysontang

DeltaTask MCP Server

by brysontang

list_tasks

Retrieve all tasks from your task management system, optionally filtered by specific tags to organize and view your workload.

Instructions

List all tasks with optional tags, if you user asks for a tag, please provide it in the request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:65-68 (handler)
    MCP tool handler for 'list_tasks'. Decorated with @mcp.tool(), it accepts an optional list of tags and delegates to TaskService.get_all_tasks(tags=tags). The type hints define the input schema (tags: list[str]) and output (list[dict[str, Any]]).
    @mcp.tool()
    async def list_tasks(tags: list[str] = None) -> list[dict[str, Any]]:
        """List all tasks with optional tags, if you user asks for a tag, please provide it in the request."""
        return service.get_all_tasks(tags=tags)
  • Core helper method in TaskService that implements task listing logic. Called by the list_tasks tool handler. Filters tasks by tags (among other params), retrieves from repository, and recursively adds subtasks for top-level tasks.
    def get_all_tasks(self, include_completed: bool = False, 
                    parent_id: Optional[str] = None,
                    tags: List[str] = None) -> List[Dict[str, Any]]:
        """Get all tasks with optional filtering and their subtasks."""
        # Get tasks from database
        tasks = self.repository.get_todos(include_completed, parent_id, tags)
        
        # Only add subtasks for top-level tasks
        if parent_id is None:
            for task in tasks:
                self._recursively_add_subtasks(task)
        
        return tasks
Behavior2/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 mentions that tags are optional and how to handle user requests for tags, but fails to describe key behaviors such as pagination, sorting, rate limits, authentication needs, or what the output looks like. This leaves significant gaps for a tool that likely returns a list of tasks.

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

Conciseness4/5

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

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It front-loads the core purpose and includes the key detail about tags. However, the phrasing 'if you user asks' contains a minor grammatical error ('you user' instead of 'the user'), slightly detracting from clarity.

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 that there is an output schema (which should document return values), the description doesn't need to explain outputs. However, for a list tool with no annotations and low schema coverage, it should provide more context on behavior (e.g., pagination, limits) and parameter usage. The description is minimally adequate but has clear gaps in completeness.

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

Parameters2/5

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

The input schema has 0% description coverage, so the description must compensate. It explains that 'tags' is an optional parameter for filtering, which adds some meaning beyond the schema's type definition. However, it doesn't clarify the semantics of the tags (e.g., how they match tasks, if multiple tags are AND/OR logic), leaving the parameter only partially documented.

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 verb ('List') and resource ('all tasks'), making the purpose understandable. It also mentions optional filtering by tags, which adds specificity. However, it doesn't explicitly differentiate this tool from sibling tools like 'search_tasks' or 'get_all_tags', which prevents a perfect score.

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?

The description provides implied usage by mentioning that tags are optional and should be included if the user asks for them. However, it lacks explicit guidance on when to use this tool versus alternatives like 'search_tasks' or 'get_all_tags', and doesn't specify any exclusions or prerequisites.

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/brysontang/DeltaTask'

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