Skip to main content
Glama

Coline

Read a project's or cycle's activity

read_scope_activity
Read-onlyIdempotent

Lists changes across the tasks in a project or cycle, newest first, optionally by one person or one kind of change. Only tasks on boards the person can open.

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>",
      "scopeKind": "<scopeKind>",
      "scopeId": "<scopeId>"
    },
    "name": "read_scope_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
cursorNo
scopeIdYes
scopeKindYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
actorUserIdNo

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
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, yet the description still adds real value: result ordering ("newest first") and a permission-based visibility rule ("Only tasks on boards the person can open"). It does not disclose pagination behavior or the default page size, which is the main 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?

Two tight sentences with the core purpose front-loaded and the ordering/filtering details following immediately; the visibility caveat is short and earns its place. Slightly fragmentary phrasing ("Only tasks on boards the person can open") is acceptable but not polished.

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 values need not be explained, but for a paginated list tool the description never mentions limit/cursor or the default of 50 and 200 max, nor does it clarify the required workspace/scopeKind/scopeId trio. Given three required parameters and 14% schema coverage, the definition is workable but leaves meaningful 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 very low at 14%, so the description must carry parameter meaning, and it only partly does: "optionally by one person" maps to actorUserId and "one kind of change" maps to the kind enum. It says nothing about workspace, scopeKind/scopeId selection, or what limit/cursor control, leaving most of the seven parameters undocumented.

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 ("Lists changes across the tasks") plus the scope ("in a project or cycle"), which distinguishes it from siblings like read_board_activity and read_cycle. It never names those siblings explicitly, so differentiation is implied by scope rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named; the agent must infer that read_board_activity covers boards and this covers projects/cycles. The only routing-adjacent statement, "Only tasks on boards the person can open," is a visibility constraint rather than usage guidance.

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