Skip to main content
Glama

Create subtask

create_subtask

Create a subtask under a task. All time entries are logged against subtasks, so every task needs at least one. The subtask inherits a valid billing type from the parent task. Discover ids with find_billing_work - never ask the user for an id.

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": {
      "task_id": "<task_id>",
      "name": "<name>"
    },
    "name": "create_subtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSubtask name (required).
task_idYesId of the parent task (required). Must be a task in your organization.
descriptionNoOptional subtask description.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare creation semantics (readOnlyHint=false, destructiveHint=false), so the lower bar applies. The description adds genuinely useful behavioral context: subtasks inherit a valid billing type from the parent, and time entries are only logged against subtasks. It omits what happens if the parent has no valid billing type (failure mode) and does not mention the response, though the idempotency_key parameter implies retry behavior that the description never explains.

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?

Three tight sentences, front-loaded with the action, then the domain constraint that motivates it, then the id-discovery instruction. No filler or redundancy.

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

Completeness4/5

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

For a four-parameter mutation tool with full schema coverage and annotations covering the safety profile, the description supplies the key domain rule (billing-type inheritance) and the id workflow. The remaining gap is failure behavior when the parent lacks a valid billing type, plus the absence of an output schema leaves the caller unsure what identifier the new subtask returns.

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?

Schema coverage is 100%, so the baseline is 3. The description adds a small amount beyond the schema by implying where task_id values come from (find_billing_work), but it says nothing about name uniqueness, description usage, or what idempotency_key means in practice.

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 opens with a specific verb and resource ("Create a subtask under a task") and states the parent relationship, which distinguishes it from the sibling create_task. It stops short of explicitly contrasting with create_task or explaining when a subtask rather than a top-level task is appropriate.

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

Usage Guidelines4/5

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

It gives concrete workflow guidance — "Discover ids with find_billing_work - never ask the user for an id" — naming the exact sibling to use for id resolution. It does not state any when-not-to-use conditions or prerequisites such as permissions on the parent task.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources