Retrieve all tasks from a specified KanbanFlow board using the board name, so you can review or process every task in one response.
Get every task on a board.
| Name | Required | Description | Default |
|---|---|---|---|
| board_name | Yes | Name of the configured board to operate on (see list_boards) |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral context. The verb 'Get' implies a read, but it says nothing about pagination, ordering, permissions, or result volume for what could be a large list. That is a significant gap for a list tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no waste, but under-specified for a list tool. Conciseness here tips into thinness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No annotations, no output schema, and no return/ordering/pagination detail. For a board-wide task retrieval tool this leaves the agent unable to predict result shape or size.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the board_name parameter is fully documented in the schema including a pointer to list_boards. The description adds no meaning beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Get every task') and scopes it to 'a board'. It doesn't differentiate itself from the close sibling 'get_tasks_by_column', leaving ambiguity about whether filtering is possible.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance and no alternatives named. With siblings like get_tasks_by_column and get_task present, the agent gets no help choosing between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.