Frostbyte

get_task

Read-onlyIdempotent

Get full details for a task including checklists, blocker, agent context, recent comments and attachments. When the task lists attachments and its text mentions a screenshot, mockup, design or other visual cue, read them with get_task_attachment before starting.

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": "get_task"
  }
}

Input Schema

Name	Required	Description
`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.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds value beyond that by disclosing the return surface (checklists, blocker, agent context, recent comments, attachments), which matters since no output schema exists, and by prescribing a follow-up step when visual attachments are present.

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?

Two sentences, no filler. The core capability is front-loaded in sentence one, and sentence two carries a concrete conditional workflow instruction rather than restating the title.

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?

A read-only, three-parameter fetch tool with a fully documented schema and no output schema. The description adequately compensates by naming what the response includes and how to handle the attachment case. Minor gap: no note on size or truncation behavior for large comment/attachment sets.

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%: taskId documents the 'FB-360 or 360' format, projectId is identified, and context carries a detailed analytics-purpose spec. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('Get full details for a task') and enumerates the payload contents (checklists, blocker, agent context, comments, attachments). This clearly separates it from list_tasks (summary listing) and get_task_attachment (raw file retrieval), which the description explicitly defers to.

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?

Provides an explicit conditional rule: when the task lists attachments and the text mentions a screenshot, mockup or design cue, call get_task_attachment before starting work. That is real when-to-use routing to a sibling. It stops short of stating when to prefer list_tasks or get_project instead, so it is clear context without full exclusion coverage.

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?