Skip to main content
Glama

list_lanes

Read-onlyIdempotent

Fetch lanes for a Kaiten board by board ID, returning each lane's ID, title, and order.

Instructions

List lanes on a board (id, title, order).

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": {
      "board_id": "<board_id>"
    },
    "name": "list_lanes"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds only the shape of each returned lane, which the output schema also covers, and says nothing about result ordering, pagination, or what happens when the board has no lanes.

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?

One short sentence, front-loaded with the verb and resource, with zero filler. The parenthetical return-field list is mildly redundant with the output schema but costs almost nothing.

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?

For a single-parameter, read-only list tool with a full annotation set and an output schema, the description covers the action, the scope and the returned fields. Ordering and empty-result behavior are the only omissions, and both are minor at this complexity.

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 0%, but the single parameter is board_id and the phrase "on a board" makes its meaning obvious, so the description effectively compensates for the gap. It adds no detail on format, validity, or behavior for an unknown board id, so it does not exceed baseline.

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 gives a specific verb and resource ("List lanes on a board") and even names the returned fields (id, title, order), which separates it from list_boards, list_columns and list_tasks. It stops short of explicitly contrasting itself with those siblings, so it lands just below the top mark.

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 statement of when to use this tool, when not to, or which sibling to prefer — notable given list_columns and list_tasks sit alongside it. The required board_id implies the tool operates per-board, but that is inference, not guidance.

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