Skip to main content
Glama

Coline

Read a board's activity

read_board_activity
Read-onlyIdempotent

Lists changes across all tasks on a board, newest first, optionally by one person or one kind of change.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
cursorNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
actorUserIdNoOnly changes by this person, or by agents working for them.
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
changesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

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=false, so the safety profile is fully covered. The description adds one genuine behavioral fact not in the annotations: results are ordered newest first. It says nothing about paging behavior (cursor/limit interplay) or how much history is retained, which is the remaining gap.

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?

A single front-loaded sentence with no filler; the scope ('across all tasks on a board') and ordering come first and the modifiers come last. It is efficient, though it is perhaps too terse for a six-parameter paginated tool.

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?

An output schema exists, so return shape need not be described, and the read-only annotations carry the risk profile. However, for a paginated six-parameter activity feed with an enumerated change kind, the description omits pagination guidance and does not explain what the kind values mean, leaving the agent to guess.

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 33%, so only workspace and actorUserId are self-documenting; the description partially compensates by implying the actorUserId and kind filters, but leaves kind's seven enum values, limit's 50/200 bounds, and cursor usage entirely to the schema. It adds meaning over the raw schema but does not close the coverage gap.

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 ('lists changes across all tasks on a board'), plus ordering ('newest first') and filterable dimensions. It does not name or differentiate itself from plausible siblings such as read_task_history, read_scope_activity, or get_crew_activity, so the agent must infer the boundary itself.

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?

Use is only implied through the filtering language ('optionally by one person or one kind of change'), which suggests audit/review scenarios. There is no explicit when-to-use, when-not-to-use, or pointer to the board-scoped vs task-scoped or workspace-scoped activity alternatives in the sibling list.

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