taskboi

get_subtasks

Retrieve all subtasks for a given parent task ID to view hierarchical task breakdowns.

Instructions

Get all subtasks of a parent task

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parentId": "<parentId>"
    },
    "name": "get_subtasks"
  }
}

Input Schema

Name	Required	Description	Default
`parentId`	Yes	The parent task ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 5, 2026

TDQS

B3.3/5.0

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 simply states the operation without mentioning ordering, recursion depth (e.g., whether nested subtasks are included), error behavior, or return format. This is minimal but not misleading.

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 a single clear sentence with no filler. It is front-loaded and immediately conveys the action and target resource.

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 tool's simplicity, the description is adequate but leaves gaps: it does not explain the return value shape, whether subtasks are returned recursively, or what happens if the parent ID does not exist. There is no output schema or annotations to compensate, so an agent may need additional context.

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 schema has 100% coverage for the single parameter parentId, already describing it as 'The parent task ID'. The tool description adds no additional parameter semantics beyond restating that these are subtasks of a parent task, which is already implicit from the tool name and parameter name.

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 'Get all subtasks of a parent task' uses a specific verb ('Get all') and resource ('subtasks of a parent task'), clearly distinguishing it from sibling tools like list_tasks or get_task. The scope is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or conditions that would help an agent decide between get_subtasks and get_task/list_tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server