Skip to main content
Glama

get_transaction_history

Read-onlyIdempotent

Read the editor's undo history newest-first, including edits made in the UI, to see what changed, its context, target, and undo status before reverting or diagnosing.

Instructions

Read the editor's undo buffer as a list, most-recent-first: each entry's title, context, primary object and whether it has already been undone. Use it to answer "what changed the editor recently, and was it me" -- including edits made by the human in the UI -- before you undo anything or blame a tool for a state you did not expect. Pure read; get_undo_state gives the counts-only summary.

Returns: { count: int, entries: [{ queue_index: int, title: string, context: string, is_transient: bool, primary_object: string, is_undone: bool }] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_entriesNoMax entries to return, newest first (default 50, clamped to 1..500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/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 'Pure read' restates that. The description adds genuinely new context: most-recent-first ordering and the fact that entries include human UI edits, which is behavioral detail beyond annotations. It stops short of discussing limits or failure modes.

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 operation, then usage, then the alternative, then an inline return shape. Every sentence serves a purpose, though the return block and the 'was it me' phrasing add some length that could be tighter.

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?

No output schema exists, so the description carries return-value disclosure and does so fully via the inline Returns block. Combined with ordering, UI-edit coverage, and the sibling alternative, an agent has everything needed to call and interpret this tool.

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 100% and the single max_entries param is fully documented there (default 50, clamped 1..500). The description echoes the newest-first ordering but adds no format or semantics beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (read) and resource (the editor's undo buffer as an ordered list), and explicitly distinguishes itself from the sibling get_undo_state ('counts-only summary'). An agent can differentiate it from alternatives without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('before you undo anything or blame a tool for a state you did not expect') and names the alternative (get_undo_state) plus the condition that selects each. Nothing is left to inference.

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

Deploy Server

Other Tools