Skip to main content
Glama
Sign In
YNAB MCP Server

YNAB MCP Server

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Undo History

list_undo_history
Read-onlyIdempotent

Review recent local write-journal entries newest first to identify undoable changes and audit-only records; use entry IDs with undo_operation to reverse supported writes without an API request.

Instructions

Read local write journal, newest first, with undo capability. No API request. undoable:false entries are audit-only. Use entry IDs with undo_operation.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries to return (default 20, newest first)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv6.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv5.4.0
    • removedOutput schema / properties / result / description
      Removed value: -"Structured result returned by List Undo History."
  3. Addedv5.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond those annotations: this reads a local write journal rather than making an API request, ordering is newest first, and non-undoable entries are audit-only.

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?

Compact and front-loaded: the core action and scope come first, followed by the no-API clarification, audit-only caveat, and undo routing. Every phrase contributes useful information.

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?

For a simple one-parameter read tool with full schema coverage, annotations, and an output schema, the description supplies what is missing: local journal semantics, newest-first ordering, audit-only entries, and undo usage. Nothing essential for correct invocation is omitted.

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 coverage is 100%, and the limit parameter is documented with default, maximum, and ordering. The description reinforces 'newest first' but adds no parameter-specific syntax or constraints beyond the schema, so 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/resource: reading the local write journal, newest first. It distinguishes itself from API-backed siblings by saying 'No API request' and clarifies it relates to undo capability, so an agent can identify it without ambiguity.

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 clear usage context: use entry IDs with undo_operation, and undoable:false entries are audit-only. It does not explicitly contrast with sibling list_operations, but the local/no-API framing and undo routing provide actionable guidance.

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