Skip to main content
Glama
Sign In

Frostbyte

by dev.getfrostbyte
OverviewDiscussionsAdmin

task_spawn_subtasks

Break one task into steps by adding a new checklist of subtasks to it, e.g. when it turns out bigger than expected. Use create_task instead for work that ships or gets tracked separately. Each call adds a separate checklist, so put related steps in one call; repeating an identical call (same title and items) returns the existing checklist instead of a duplicate. Doesn't change the task's status. The change is audited and appears live. Returns each new subtask's text and ID, for task_edit_subtask to check off or rewrite and task_delete_subtask to remove.

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": {
      "projectId": "<projectId>",
      "taskId": "<taskId>",
      "items": "<items>",
      "context": "<context>"
    },
    "name": "task_spawn_subtasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesSubtask texts in order, each a short imperative step of up to 280 characters. 1–20 per call; a task holds at most 50 subtasks across all its checklists.
taskIdYesParent task. The task ID or number (FB-360 or 360)
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
projectIdYesThe project ID
checklistTitleNoHeading for the new checklist; longer text is cut at 80 characters (default: 'Subtasks')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / checklistTitle / description
      Previous value: -"Title for the checklist (default: 'Subtasks')"New value: +"Heading for the new checklist; longer text is cut at 80 characters (default: 'Subtasks')"
    • changedInput schema / properties / items / description
      Previous value: -"Subtask titles (1-20 items; a task holds at most 50 subtasks in total)"New value: +"Subtask texts in order, each a short imperative step of up to 280 characters. 1–20 per call; a task holds at most 50 subtasks across all its checklists."
  2. First observed

TDQS

A4.1/5.0
Behavior1/5

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

The annotations set idempotentHint=false, but the description says repeating an identical call with the same title and items returns the existing checklist instead of creating a duplicate. That describes idempotent behavior for identical arguments, directly contradicting the annotation. The rest of the description is helpful, but the contradiction forces a 1 under the rubric.

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 front-loaded with the core action and then moves efficiently through alternatives, duplicate behavior, status effects, auditability, and return values. Every sentence adds information and there is no filler.

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

Completeness5/5

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

With no output schema, the description still explains that each new subtask's text and ID are returned and points to task_edit_subtask and task_delete_subtask for follow-up. It also covers mutation, audit/live behavior, status unchanged, and duplicate handling, which is sufficient context for this tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that duplicate identity depends on the same title and items, and by advising grouping related steps into one call. It does not discuss checklistTitle truncation or context formatting, but it does add useful interpretation of the key parameters.

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?

States a specific verb and resource: breaking one task into steps by adding a checklist of subtasks. It also explicitly distinguishes this from create_task, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives a clear when-to-use scenario (when a task turns out bigger than expected) and names the alternative tool for work that ships or is tracked separately. It also advises putting related steps in one call, which is actionable invocation guidance.

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

All Frostbyte toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources