Skip to main content
Glama

History

history
Read-onlyIdempotent

Earlier versions, newest first, with who made each (a device or an AI): of a note's text, an app (code and data), or a file. A note's versions say what each change removed and added; with version, history shows that version's whole text, so you can check it before you restore 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": {
      "path": "<path>"
    },
    "name": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesA path, as list and search show them: "Work/Acme.md", a folder "Work/", a sub-note "Work/Acme/Agenda.md", a note's file "Work/Acme/contract.pdf", a file in a folder "To read/Paper.pdf", an app's file "Work/Habits.app/src/App.tsx" or its data "Work/Habits.app/data.json".
limitNoDefault 10.
versionNoA note's version from history: show its whole text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / version
      Added value: +{
      +  "description": "A note's version from history: show its whole text.",
      +  "type": "integer"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real behavioral detail beyond them: ordering is 'newest first,' each entry records 'who made each (a device or an AI),' note versions expose what was 'removed and added,' and the version parameter expands one entry to its 'whole text.' It omits pagination behavior and what happens with limit on version lists, so a 4 rather than 5.

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?

It front-loads the essentials — 'Earlier versions, newest first, with who made each' — then qualifies entity types and the version-expansion behavior. It is dense but every clause carries information; only the parenthetical 'app (code and data)' feels slightly compressed rather than wasteful.

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?

For a read-only history tool with no output schema, the description covers ordering, authorship attribution, diff semantics for notes, and the version-expansion mode. Missing is how limit interacts with versions or whether history paginates, which leaves a small but real gap for an agent iterating over long histories.

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%, so path examples (note, folder, sub-note, app file, app data) and the limit default of 10 are already documented in the schema. The description reinforces the note-version expansion behavior of the version parameter but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description clearly states the resource and scope: 'Earlier versions, newest first, with who made each... of a note's text, an app (code and data), or a file.' That tells an agent this returns version history with authorship across three entity types, which distinguishes it from siblings like restore or edit without naming them. A specific verb is only implied by the noun 'history,' keeping it just short of a 5.

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?

Usage context is explicit and tied to a real workflow: 'with version, history shows that version's whole text, so you can check it before you restore it,' which positions it ahead of restore. There are no stated exclusions or named alternatives, so it does not reach 5, but an agent knows why and when to call it.

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.