Skip to main content
Glama

KanbanMCP

Claim the next card

claim_next

Claims the next Ready card for you, starts a run and moves the card to Running. Pass cardId to work one exact card. Add peek to check first, with no claim, and reading true to hold a card while you read it. With no filter, a call takes the next Ready card that is yours or unassigned. A card assigned to another persona never comes to you. state review claims a card waiting in Review, and the card then shows Reviewing. If you start sub-agents, give each one its own runtimeHandle.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "claim_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
peekNoClaim nothing; show the result.
stateNoready (the default) or review.
cardIdNoWork this one card: a number like ABC-12, or an id. The filters are ignored.
columnNoA column, by id or label.
effortNolow, medium, high or none (no effort set): any of these.
labelsNoOnly cards with any of these labels.
boardIdNoBoard id or slug.
cardIdsNoCards to claim as one batch. Send more to add to it.
contextNoPass full to get every piece of context again.
effortsNoWith cardIds: card to low, medium or high, if unset.
excludeNoCards to skip, by id or number.
personaNoThe persona to act as.
readingNoWith cardId: a reading claim. The card does not move.
assigneeNome (only yours), a persona name, none (unassigned only) or any.
batchTitleNoWith cardIds: a batch title.
minPriorityNoOnly cards with at least this priority.
runtimeHandleNoA short name for this agent or sub-agent. Use a different one for each sub-agent.
acknowledgeOverlapNoClaim a card whose files overlap a running card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With annotations only declaring readOnlyHint=false and destructiveHint=false, the description carries the real disclosure: the card is moved to Running and a run is started, peek performs no claim, reading holds a card without moving it, state=review transitions the card to Reviewing, and cards assigned to another persona are never returned. These are exactly the mutation and edge-case behaviors an agent must know before calling.

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?

The primary action is front-loaded in the first sentence and each following sentence adds a distinct usage rule with no filler. There is mild redundancy between 'claims the next Ready card for you' and the later restatement of the no-filter behavior, but it is acceptable for an 18-parameter tool.

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

Completeness4/5

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

For a mutation tool with no output schema, the description covers the core claim/run/move semantics, the peek and reading variants, and the cross-persona rule. It does not describe batching (cardIds/batchTitle/efforts) or acknowledgeOverlap, which are meaningful capabilities an agent could otherwise miss.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the workflow meaning of peek, reading, cardId (filters ignored) and state=review, and the sub-agent runtimeHandle convention. It adds real semantic nuance, though it omits the batch parameters (cardIds, batchTitle, efforts) and filters like exclude/minPriority.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a precise verb+resource (claims the next Ready card) plus the concrete side effects (starts a run, moves the card to Running), which immediately separates it from read-only siblings like find_cards or show. It also states the no-filter default scope (yours or unassigned), so an agent knows exactly what a bare call does.

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

Usage Guidelines4/5

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

It gives clear conditional guidance: pass cardId to work one exact card, peek to check without claiming, reading to hold while reading, state=review for the Review queue, and a distinct runtimeHandle per sub-agent. It never names sibling alternatives (find_cards, release, show) for when-not-to-use, so it stops short of the top tier.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources