Skip to main content
Glama

get_task_history

Read-onlyIdempotent

Retrieve a task's change log to see who changed what and when, including title, notes, assignees, board, deadline, and completion, ordered oldest first.

Instructions

Change log of a task: who changed what (title, notes, assignees, board, deadline, completion...) and when, oldest first.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by specifying the sort order ('oldest first') and the range of change types captured, which the annotations and one-parameter schema do not convey.

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 sentence with the core concept front-loaded, followed by a compact parenthetical field list and the ordering guarantee. No filler, no restatement of the tool name alone, and nothing that could be cut without losing information.

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?

This is a simple read-only tool with one parameter and an output schema, so return values need not be explained; the description covers scope, tracked fields, and ordering. Minor gaps — whether history is bounded or paginated and whose perspective 'who' reflects — are small relative to the tool's simplicity.

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 0%, but there is only one required parameter (task_id) and the description's phrase 'of a task' makes its role unambiguous. It adds no format, ID-type, or validation detail beyond the schema, so it sits at the adequate baseline rather than compensating 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 uses a specific verb+resource pairing — 'Change log of a task' — and immediately enumerates what is tracked (title, notes, assignees, board, deadline, completion), which implicitly distinguishes it from get_task (current state) and get_task_comments. An agent knows exactly what this returns without opening the schema.

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 it should call this when it needs audit/history data rather than current task state, but the description never says so explicitly. It names no alternative (e.g. get_task for current values) and states no prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.