Frostbyte

list_tasks

Read-onlyIdempotent

List tasks in a project. Defaults to active work only (todo + in-progress) — pass status "done" or "all" only when completed work is actually needed. Filter by releaseId/areaId/search instead of fetching everything.

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

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1)
`limit`	No	Tasks per page (max 100, default: 25)
`areaId`	No	Only tasks assigned to this area
`search`	No	Case-insensitive substring match on task titles
`status`	No	Status filter (default: "active" = todo + in-progress). "done" lists completed tasks most-recent first.
`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
`releaseId`	No	Only tasks assigned to this release

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's real add is the default scope (active = todo + in-progress) and the recency ordering note implied for done — useful behavior beyond annotations. It does not cover pagination defaults or result volume, which would push this higher.

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, zero filler, each carrying a distinct instruction — default scope first, then narrowing guidance. Front-loaded and directly actionable.

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 read-only list tool with full annotation coverage and a fully documented schema, the description supplies the one thing structured fields can't: the intended default scope and how to narrow. Missing only return-shape or pagination expectations, which the page/limit schema entries largely carry.

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 a 3 is the floor, but the description adds decision-level meaning: the default status semantics and the instruction that filters should be used instead of broad fetches. That reframes the optional filter parameters as preferred narrowing tools rather than optional extras.

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?

"List tasks in a project" gives a specific verb and resource, and the status/filter guidance implicitly separates it from get_task (single task) and tasks_list_blocked (blocked work). It stops short of naming a sibling alternative explicitly, so it falls just under a 5.

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?

Explicit directional guidance: default is active-only work, and "done"/"all" should be requested only when completed work is actually needed, plus a strong steer to filter by releaseId/areaId/search rather than fetching everything. What it lacks is a named alternative for cases like blocked tasks (tasks_list_blocked) or cross-project listings (list_projects).

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?