Skip to main content
Glama

Coline

Show a board

show_board
Read-onlyIdempotent

Shows a board to the person inside the chat, live: they see tasks appear and move as they change, and can drag, open and edit them. Use it when the person wants to see or work on a board, or after adding several tasks.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>"
    },
    "name": "show_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
statusesYes
taskboardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the board renders live and that the user gets an interactive surface where tasks appear and move. That interactivity is genuinely new context an agent cannot infer from readOnlyHint/idempotentHint, and it also warns that the person may begin editing through the UI. It does not say what happens on failure (missing workspace or board id), which keeps it below a 5.

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?

A single compact sentence pair that front-loads the effect (live board in chat) and then the trigger. Every clause carries information: delivery target, liveness, interactivity, and usage condition.

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?

Annotations cover the safety profile, the schema covers both parameters, and an output schema exists, so the description only needs to explain the effect and the trigger, which it does. The one gap is failure or edge behavior when the board or workspace is invalid, though for a read-only presentation tool that is a minor omission.

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%, with both workspace and taskboardId documented inline including where their values come from. The description adds no parameter-level meaning on top of that, so the baseline 3 applies.

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 opens with a specific verb and resource ("Shows a board") and immediately qualifies the mode of delivery ("to the person inside the chat, live"). The resource is unambiguous against the show_* siblings such as show_calendar, show_doc, and show_sheet, so an agent can route by resource without opening any schema.

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 explicit triggering conditions: when the person wants to see or work on a board, or after adding several tasks. That is clear positive guidance, but there is no when-not guidance and no named alternative (for example a non-visual read of the board) to route to.

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