Skip to main content
Glama

list_siblings

View all sibling tasks in a hierarchical task management system to understand your position in the current task sequence, including both pending and completed tasks.

Instructions

See all sibling tasks to the left of current focus. May include both pending and completed tasks. Helpful for understanding your position in the current task sequence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_bodyNoInclude task body content

Implementation Reference

  • The main handler function that executes the list_siblings tool. It retrieves siblings from task_manager and formats the response with optional body inclusion.
    async def handle_list_siblings(self, include_body: bool = False) -> Dict[str, Any]:
        siblings = self.task_manager.list_siblings()
        return {
            "count": len(siblings),
            "siblings": [
                {
                    "id": s.id,
                    "title": s.title,
                    "status": s.status.value,
                    "created_at": s.created_at.isoformat(),
                    **({"body": s.body} if include_body else {}),
                    **(
                        {"completed_at": s.completed_at.isoformat()}
                        if s.completed_at
                        else {}
                    ),
                }
                for s in siblings
            ],
        }
  • The Tool schema definition for list_siblings, including input schema for the optional include_body parameter.
    Tool(
        name="list_siblings",
        description="See all sibling tasks to the left of current focus. May include both pending and completed tasks. Helpful for understanding your position in the current task sequence.",
        inputSchema={
            "type": "object",
            "properties": {
                "include_body": {
                    "type": "boolean",
                    "description": "Include task body content",
                    "default": False,
                }
            },
        },
    ),
  • src/server.py:70-72 (registration)
    Registration of the list_siblings tool in the server handler_map, mapping the tool call to the appropriate handler method.
    "list_siblings": lambda: handlers.handle_list_siblings(
        arguments.get("include_body", False)
    ),
  • Helper method in TaskManager that lists siblings by delegating to get_siblings_to_left().
    def list_siblings(self) -> List[SubTask]:
        return self.get_siblings_to_left()
  • Core helper function that computes the list of sibling subtasks to the left of the current task.
    def get_siblings_to_left(self) -> List[SubTask]:
        if self.is_zen_state or not self.global_tasks:
            return []
    
        last_main_task = self.global_tasks[-1]
        current = self.current_task
    
        if isinstance(current, MainTask) or not last_main_task.sub_tasks:
            return []
    
        return last_main_task.sub_tasks[:-1]
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 mentions behavioral aspects like including 'both pending and completed tasks' and being 'left of current focus', but lacks details on permissions, rate limits, or response format. For a tool with no annotations, this leaves significant gaps in understanding its operation.

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 two sentences, front-loaded with the core purpose and followed by additional context. It's efficient with no wasted words, though it could be slightly more structured by separating usage guidance into a distinct part.

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 no annotations, no output schema, and a simple input schema, the description provides basic purpose and context but lacks details on return values, error handling, or deeper behavioral traits. It's minimally adequate for a read-only tool but doesn't fully compensate for the missing structured data.

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

Parameters3/5

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

The input schema has 100% description coverage, with one parameter 'include_body' fully documented. The description doesn't add any parameter-specific information beyond the schema, such as examples or implications of setting 'include_body' to true. Baseline 3 is appropriate since the schema handles the parameter documentation.

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 tool's purpose: 'See all sibling tasks to the left of current focus' with the verb 'see' and resource 'sibling tasks'. It distinguishes from siblings like 'get_current_task' (single task) and 'get_completed_tasks' (all completed tasks) by focusing on leftward siblings. However, it doesn't explicitly contrast with 'get_stack_overview' which might show a broader view.

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 implies usage context: 'Helpful for understanding your position in the current task sequence' suggests using it when orientation is needed. It doesn't provide explicit when-not-to-use guidance or name alternatives like 'get_stack_overview' for different perspectives, leaving some ambiguity.

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/cheezcake/aidderall_mcp'

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