Skip to main content
Glama

Coline

Get crew activity

get_crew_activity
Read-onlyIdempotent

Shows what a crew member is working on, what waits on the person (to approve in Coline), and what they finished recently.

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>",
      "agentUserId": "<agentUserId>"
    },
    "name": "get_crew_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
agentUserIdYesCrew member id from list_crew.

Output Schema

NameRequiredDescriptionDefault
reviewUrlYes
inProgressYes
recentlyDoneYes
waitingOnYouYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds genuine context by disclosing the three result buckets and that one bucket is tied to an external approval system (Coline). It does not define how far back 'recently' reaches or whether results are paginated.

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 or repetition. Slight awkwardness in 'what waits on the person' keeps it from being maximally tight, but no sentence is wasted.

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?

An output schema exists, so return values need no explanation here, and the two required parameters are fully documented in the schema. The remaining gap is the undefined 'recently' window and the absence of any pointer to the board/scope activity siblings, which matters given how many related read tools exist.

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?

Both parameters are fully documented in the schema, including where each value comes from (workspaces.list for the slug, list_crew for the member id). The description adds nothing beyond that, which is acceptable at 100% coverage but earns no extra credit.

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 names a specific resource (a crew member) and enumerates the three things returned: current work, pending approvals in Coline, and recent completions. That is far more informative than the title alone. It stops short of distinguishing this from sibling reads like read_board_activity or read_scope_activity, so an agent must infer the person-centric vs. board/scope-centric split.

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 when-to-use statement, no prerequisite, and no named alternative. The description only says what data is shown, leaving the agent to guess that this is the per-person view and that read_board_activity or read_scope_activity cover the other axes.

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