Skip to main content
Glama

Coline

Read a task's history

read_task_history
Read-onlyIdempotent

Lists every change to a task (who made it, what changed, why, with evidence), plus the threads, mail, change requests and other work linked to it.

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>",
      "taskId": "<taskId>"
    },
    "name": "read_task_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
changesYes
createdYes
linkedWorkYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/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 covered. The description adds genuine value beyond that by disclosing the aggregation behavior — that results include not just field changes but also linked threads, mail, change requests and other work — which an agent could not infer from the annotations. It stops short of mentioning pagination, result limits, or ordering.

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 front-loaded sentence with a compact parenthetical that carries the substantive detail. There is no filler, hedging, or restatement of the title, and the most important information (what is listed) comes first.

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-value explanation is not required, and the annotations cover the safety profile. However, for a three-parameter tool with two undocumented identifiers, the description leaves the agent guessing about how taskboardId relates to taskId and about result size or ordering, which is a meaningful gap for a history/audit read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: workspace is documented in the schema, but taskId and taskboardId have no descriptions anywhere. The description adds no parameter meaning at all — it does not explain the taskId/taskboardId pairing or the expected identifier format — so it fails to compensate for the coverage gap.

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 names a specific verb and resource ("Lists every change to a task") and enumerates the scope of what is returned: who made the change, what changed, why, with evidence, plus linked threads, mail, change requests and other work. That scope detail distinguishes it from siblings like read_task_state or read_task_view, which imply current-state reads rather than a change log.

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?

Usage is only implied: an agent can infer this is the tool for auditing a task's evolution, but the description never states when to prefer it over read_task_state, read_board_activity, or list_task_relations, nor any exclusions or prerequisites. No explicit when/when-not guidance is present.

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