Skip to main content
Glama

Record history

record_history
Read-onlyIdempotent

Retrieves a record's commit history on a branch, with authors, messages, and optional diffs, to explain why the record is as it is and who decided.

Instructions

The commits on a branch that touched one record, newest first, each with its author and its message: the message is the reason given for the change, and a commit an assistant made for a person names that person. Pass diff to see what each commit changed in the record. Use it to answer why a record is as it is and who decided.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "record_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe record's id, as Type/local (LearningObjective/lateral-reading-check) or the local part alone.
diffNoInclude each commit's change to the record. Off when left out.
typeYesThe record's class, such as LearningObjective, AssessmentItem, Module or DesignNote.
countNoAt most this many commits; the hub gives 20 when left out.
startNoCommits to skip from the newest, for the next page.
branchNoThe branch whose commits to read; the default branch when left out. History follows a branch, not a single commit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds ordering (newest first), the diff mode, and interpretive context about who a commit author is when an assistant acted for a person. It does not cover pagination defaults or total counts, which remain schema-only.

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?

Front-loaded with the core result shape, then the diff hint, then the use case. The clause explaining message/author attribution is slightly wordy but adds genuine meaning, so nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six parameters, no output schema, and the description still conveys the return shape (per-commit author and message, newest-first ordering) plus the optional diff payload. That is enough for an agent to call it correctly without further documentation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an increment by explaining the payoff of diff ("see what each commit changed in the record") rather than just naming it. It leaves count, start and branch to the schema, which is acceptable given full coverage.

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 resource and scope: commits on a branch that touched one record, newest first, with author and message. It implicitly distinguishes itself from current-state readers like get_record by framing the output as history, but it never names a sibling to contrast with.

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

Usage Guidelines4/5

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

Gives a clear use context: "Use it to answer why a record is as it is and who decided," which is a real task framing rather than a restatement. It offers no when-not guidance or named alternative such as compare_record or branch_changes, so it stops short of a 5.

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