Skip to main content
Glama

Read a document's history

folio_history
Read-onlyIdempotent

Read a document's version history, newest first, to see how a passage or value changed and when across commits, saves, deleted files, block revisions, and embed results.

Instructions

Read a document's versions, newest first, merged from its git commits and every save Folio saw - a document since deleted included. With version, that version's full text; with block, each text the block has had; with reference, each result that embed has shown. Use it to answer how a passage or a value changed and when; for everything that changed in the folder over a period use folio_digest. Give at most one of version, block and reference. Answers {path, versions: [{id, at: ISO time, seen: a list of saved, committed and file, by: the commit's author, removed}]}, {path, version, text: null when unknown}, {path, block, versions: [{version, at: ISO time, text: absent where the block was not there}]} or {path, reference, results: [{at: ISO time, value or table, error}]}. A list cut to fit one answer adds omitted, the entries each list left out, and narrow, how to ask for less.

Input Schema

NameRequiredDescriptionDefault
pathYesThe document's path, relative to the served folder or absolute under it, such as notes/plan.md, also one since deleted
blockNoA block's id as folio_document lists it, for each text the block has had
versionNoA version's id from this tool's versions, for that version's text
referenceNoAn embed's reference as the document writes it, such as #totals#0.n, for each result it has shown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses ordering, data sources, deleted-document inclusion, conditional mode outputs, and truncation behavior with omitted and narrow. This is rich behavioral context that the readOnly and idempotent annotations alone do not provide.

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?

The description is dense but front-loaded, beginning with the core purpose and then covering modes, alternatives, and return shapes. Every sentence carries useful information, including the compact output schema summaries and truncation behavior.

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?

With no output schema, the description supplies the relevant return shapes for all modes and explains what omitted and narrow mean when results are cut. For a four-parameter read tool with complex mode-dependent outputs, this is complete enough for correct invocation.

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 schema already documents each parameter. The description still adds meaningful semantics: version returns that version's full text, block returns each text the block has had, reference returns each result the embed has shown, and at most one of the three may be supplied.

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 states a specific verb and resource, reading a document's versions, and explains the merge from git commits and Folio saves, including deleted documents. It also distinguishes mode-specific behavior and names folio_digest for the folder-wide alternative, so an agent can identify the tool 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 Guidelines5/5

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

It gives explicit when-to-use guidance: answer how a passage or value changed and when. It names folio_digest as the alternative for everything that changed in the folder over a period, and it states the key constraint to give at most one of version, block, and reference.

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