Skip to main content
Glama

Compare Snapshot

compare_snapshot
Read-onlyIdempotent

Compare a document snapshot to the current text or another snapshot, showing added and removed paragraphs and net word count change.

Instructions

Compare a document snapshot against the current document text, or against another snapshot (pass againstSnapshotId). Returns the paragraphs added and removed and the net word-count change — use this to see what changed since a snapshot was taken. Read-only. Requires an open project (call open_project first). Get snapshot ids from list_snapshots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYesUUID of the document.
snapshotIdYesThe baseline snapshot id (from list_snapshots).
againstSnapshotIdNoOptional second snapshot id to compare against. Omit to compare against the current document text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesWhat it was compared against ("current" or a snapshot id).
fromYesThe baseline snapshot.
wordDeltaYesto.wordCount minus from.wordCount (negative means text was cut).
documentIdYes
wordsAddedNoWords present in the compared-to text but not the snapshot (word-level).
wordsRemovedNoWords present in the snapshot but not the compared-to text (word-level).
addedParagraphsYesParagraphs present in the compared-to text but not the snapshot.
removedParagraphsYesParagraphs present in the snapshot but not the compared-to text.
unchangedParagraphsNoCount of paragraphs common to both.
Behavior4/5

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

Declares read-only behavior, aligning with annotations. Adds detail on required open project and output structure. Annotations already cover safety, so description adds useful behavioral context beyond annotations.

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?

Three sentences with front-loaded core action, then details. No filler, every sentence adds value.

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?

Given the presence of an output schema and the description's coverage of return values, prerequisites, and parameter usage, it is fully adequate for an agent to use the tool correctly.

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 description coverage is 100%, and description provides additional context for snapshotId (baseline) and againstSnapshotId (optional second snapshot), clarifying their roles beyond schema definitions.

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?

Clearly states it compares a document snapshot against current text or another snapshot, and specifies return values (paragraphs added/removed, net word-count change). Distinguishes from siblings like list_snapshots and read_snapshot.

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?

Explicitly says when to use (to see changes since a snapshot), mentions prerequisite of an open project, and instructs how to get snapshot IDs. Also explains optional againstSnapshotId usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/writerslogic/scrivener-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server