Frostbyte

task_start

Destructive

Move a task to in-progress when you begin work on it the user asked for; a whats_next recommendation alone doesn't authorise starting. Call get_task first to read it and check its status. Accepts a todo task, or a blocked task to resume (this clears its blocker). Refuses a task already in progress (just carry on working) or done (ask which task they meant). Doesn't assign the task or change other fields; use update_task for those. Logs the start in the activity feed, updates the board live and syncs a linked GitHub issue. Returns the new status and the owner's Current Focus, if set. Finish with task_complete.

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>",
      "context": "<context>"
    },
    "name": "task_start"
  }
}

Input Schema

Name	Required	Description
`note`	No	Optional one-line reason, added to the activity entry (e.g. resuming after a blocker, switching from another task). Usually omit.
`taskId`	Yes	The task ID or number (FB-360 or 360)
`context`	Yes	Explain 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."
`projectId`	Yes	The project ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / note / description

Previous value: -"Optional one-line note on why now (resuming, switching tasks). Usually omit."New value: +"Optional one-line reason, added to the activity entry (e.g. resuming after a blocker, switching from another task). Usually omit."

First observedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses side effects: logging to the activity feed, live board updates, GitHub issue sync, and clearing a blocker when resuming a blocked task. It also documents refusal behavior for in-progress and done tasks and describes return information.

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 dense but front-loaded, starting with the core action and authorization condition. Every sentence contributes guidance about prerequisites, accepted states, side effects, or follow-up actions.

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?

Given four parameters, no output schema, and the supplied annotations, the description covers the workflow, state acceptance, side effects, refusals, and return information sufficiently for correct invocation.

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 description coverage is 100%, so the schema already explains taskId, note, context, and projectId. The description adds workflow meaning but no additional parameter syntax or constraints beyond what the schema provides.

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 uses a specific verb and resource: moving a task to in-progress when work begins. It distinguishes this from adjacent tools such as update_task, task_complete, and whats_next by explaining that a recommendation alone does not authorize starting.

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?

It explicitly states when to call it, that get_task should be called first, which task states are accepted, and which states are refused. It also names update_task as the alternative for assignment or field changes, leaving little ambiguity.

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

All Frostbyte tools Inspect

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

Need Help?