Skip to main content
Glama
opositatest

swimlane-mcp

by opositatest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_tasks

Read-onlyIdempotent

List KanbanFlow tasks for a person across configured boards, optionally filtered by board or column, with resolved names, counts, and load warnings.

Instructions

Lists the tasks of one person across every configured KanbanFlow board (or the boards you choose), optionally only in some columns. By default the person is the configured user ("me"). Returns how the person was matched on each board, the tasks with board, column, swimlane, color, labels and people resolved to names, counts per board and column, and a meta block that reports boards where the person is not a member, filters that matched nothing and columns that were only partially loaded. The server does not rank or classify tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum tasks returned (default 50, max 500). Counts always cover every match.
boardsNoBoard ids or exact names to search (see list_boards). Default: every configured board.
detailNo"summary" (default) trims descriptions. "full" adds the complete description and the raw API object.
personNoWhose tasks: user id, email, full name or part of the name. Omit it (or use "me") for the configured user (KANBANFLOW_USER). A task matches when the person is its responsible user or a collaborator.
columnsNoColumn ids or exact names (case-insensitive), on any of the boards. Default: every column. Limited columns listed here (usually "done") are loaded completely.
loadAllPagesNoLoad every limited column completely, not only those in `columns` (slow on big boards).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, open-world), and the description goes well beyond that: it details the return payload, a `meta` block that flags boards where the person is not a member, filters that matched nothing and partially loaded columns, and warns that the server does not rank or classify tasks. These are genuine behavioral traits not visible in the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences that front-load the core scope and then the return shape. Every sentence carries information, though the long middle sentence listing resolved fields is slightly overloaded and could be tightened.

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 carries the return-value burden and does so: it names the fields (board, column, swimlane, color, labels, people resolved to names), the per-board/column counts, the `meta` caveat block, and the non-ranked ordering. An agent has everything needed to interpret results and pick parameters.

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 documents every parameter thoroughly, including the `person` matching rule and the `limit` default/max. The description largely restates those meanings (default person = configured user) without adding new syntax or edge-case semantics, matching the baseline for a fully documented schema.

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?

States a specific verb and resource ('Lists the tasks') plus its scope: one person, every configured KanbanFlow board, optionally limited to columns. The agent can picture the output and the scope precisely. It does not explicitly name or distinguish itself from search_tasks, but the person-centric scope is clear enough to stand apart.

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?

Provides useful defaults ('By default the person is the configured user ("me")') and hints at when the columns/loadAllPages options matter, but never says when to reach for this tool instead of search_tasks or get_task. Usage is implied rather than routed explicitly.

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

Deploy Server

Other Tools