Skip to main content
Glama

list_tasks

Read-only

List tasks in a Kanboard project, optionally filtered by status or column, to view open, closed, or all items for task tracking.

Instructions

List tasks in a project, optionally filtered by status and column.

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

Input Schema

NameRequiredDescriptionDefault
columnNoOptional column name or ID
statusNoopen
project_idYesKanboard project ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further — no pagination, result limits, ordering, or what happens when the project has no tasks — so it contributes no behavioral context beyond the structured fields.

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?

A single front-loaded sentence with the resource first and the optional filters trailing; there is no redundant or filler wording to trim.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the required project_id is clear. For a listing tool with filtering and a sibling search tool, though, the definition leaves gaps around scope, ordering, and result size that an agent might reasonably need.

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 67% and the schema already documents project_id and column while the enum constrains status. The description only restates that status and column are optional filters, adding no format or default nuance ('open' default comes from the schema), so baseline 3 is warranted.

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 states a concrete verb and resource ('List tasks in a project') plus the optional filter dimension, so an agent knows exactly what the tool returns. It does not, however, distinguish itself from the sibling 'search_tasks', leaving ambiguity about which listing tool to pick.

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

Usage Guidelines3/5

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

Usage is only implied: the phrasing 'optionally filtered by status and column' suggests a simple scoped listing, but there is no explicit when-to-use guidance, no mention of when to prefer 'search_tasks', and no stated preconditions beyond the required project.

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