Skip to main content
Glama

KanbanMCP

Find cards

find_cards
Read-onlyIdempotent

Finds cards on one board. Leave out boardId to search every board you reach. It gives one short row per card, with no description or comments.

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": "find_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
limitNo
ownerNoA person's name or id, me or none.
queryNoWords to find, and tokens: priority: (urgent, high, normal, low), effort: (high, medium, low, none), label:. Repeat priority: or effort: to match any.
quietNoOnly claims whose agent went quiet.
stateNolater, triage, todo, ready, running, blocked, review or done.
columnNoA column, by id or label.
cursorNonextCursor from the last page.
boardIdNoOne board, by id or slug. Leave it out for every board.
assigneeNoA persona name, me or none.
mentionsMeNoOnly cards with an unread mention of you.
commentedByNoA persona name or me.
hasCommentsNo
updatedSinceNoOnly cards active since this time (ms).
notCommentedByNoA persona name or me.
includeArchivedNo
unansweredQuestionNoOnly cards with an open question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds non-obvious behavior beyond that: results are one short row per card with no description or comments, warning the agent that this is a shallow projection and full content needs another tool.

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

Conciseness5/5

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

Three short sentences, zero filler, and the board-scope caveat plus the return-shape warning are front-loaded. Every sentence earns its place.

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 17-parameter, no-output-schema query tool the description is serviceable but thin: it never mentions pagination via cursor/limit or defaults, leaving the agent to infer paging from the schema alone. Adequate minimum but with clear gaps.

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 76% with 17 parameters, so the schema carries most of the burden and baseline is 3. The description only restates the boardId omission semantics rather than adding filter syntax, defaults, or pagination behavior beyond what the schema already documents.

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 ('Finds cards') plus the scope (one board, or every board if boardId is omitted), which separates it from siblings like list_boards or show. It does not explicitly name a sibling to route against, but the purpose 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 Guidelines3/5

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

'Leave out boardId to search every board you reach' is conditional guidance for one parameter, but no when-to-use-vs-alternative guidance is given (e.g., when to use this instead of show for full card details). Usage is only implied.

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