Skip to main content
Glama

list_boards

Read-onlyIdempotent

Retrieve boards within a specified Kaiten space, returning their IDs and titles to help select the right board for task management workflows.

Instructions

List boards in a space (id, title, space_id).

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": {
      "space_id": "<space_id>"
    },
    "name": "list_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYes

Output Schema

NameRequiredDescriptionDefault
countYes
itemsYes
card_idNo
_metricsNo
board_idNo
space_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world behavior, so the safety profile is fully covered without the description. The description adds no behavioral context of its own — no note on pagination, result count, ordering, or behavior for an empty/nonexistent space — and the '(id, title, space_id)' parenthetical merely restates return fields already captured by the output 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?

A single front-loaded sentence with no filler; the scope is stated before the field list. It is efficient, though its brevity borders on under-specification rather than earning every omission.

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?

For a one-parameter read tool with an output schema, the essentials (what it returns and what it filters on) are present. Still missing are any indication of result volume or pagination and what a caller should expect when the space has no boards, which matters for a list tool.

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?

The single parameter has 0% schema description coverage, so the description must carry the load. 'In a space' does tie space_id to the notion of scoping results to one space, but it gives no format, range, or validity detail beyond the parameter's own name.

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?

Names a specific verb and resource ('List boards') plus a scope modifier ('in a space'), which distinguishes it from siblings like list_spaces and list_tasks that operate on other resources. It stops short of explicitly contrasting with any sibling, but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of an alternative (e.g., listing tasks or columns instead of boards), and no stated prerequisite such as needing a valid space. The only implicit guidance is that a space_id is required, which the schema already enforces.

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