Skip to main content
Glama

KanbanMCP

Show a card

show
Read-onlyIdempotent

Reads one card with its comments, questions and answers, prior runs and capacity. Read-only; it needs no claim or persona.

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": {
      "cardId": "<cardId>"
    },
    "name": "show"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesCard id, number (12) or key (WEB-12).
boardIdNoBoard id or slug.
commentsBeforeNoOlder comments: commentsBefore from an earlier answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still adds genuine context beyond annotations: the no-claim/no-persona requirement and an inventory of the returned content (comments, questions, answers, prior runs, capacity).

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?

Two compact sentences with zero waste: the read scope and return contents come first, then the precondition. Nothing is redundant or padded.

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?

With no output schema, the description compensates well by enumerating the returned payload, and the schema fully covers parameters. It stops short of explaining pagination behavior for the commentsBefore cursor or handling when a card is not found.

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 description coverage is 100%, so cardId, boardId and commentsBefore are already documented, including the card key format and the pagination linkage for commentsBefore. The description adds no syntax or semantics beyond the schema, so the baseline 3 applies.

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 ('Reads') and resource ('one card') and enumerates what the single read returns: comments, questions, answers, prior runs and capacity. The singular scope implicitly separates it from list-style siblings such as find_cards, though no sibling is named explicitly.

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?

The clause 'it needs no claim or persona' gives a useful precondition hint, distinguishing it from claim-based siblings like claim_next and complete. However, it never says when to use this versus find_cards, get_context or inbox, leaving the routing decision to inference.

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