Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

list_note_versions

Read-only

Retrieve a note's saved versions in newest-first order to review every edit, restore, and conflict. Supports pagination for browsing version history.

Instructions

List a note's saved versions, newest first (every edit, restore and conflict is kept).

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": {
      "noteId": "<noteId>"
    },
    "name": "list_note_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 30
cursorNonextCursor from the previous page
noteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value with retention semantics ("every edit, restore and conflict is kept") and result ordering, but says nothing about pagination behavior or whether stale versions ever expire.

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?

A single sentence with zero filler, and the resource plus ordering are front-loaded before the retention detail. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description could reasonably say what a version object contains (author, timestamp, content snapshot). For a simple read-only list tool with annotated safety the definition is workable, but that gap makes it only adequate rather than complete.

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 67% and the schema already documents limit ("Default 30", max 100) and cursor ("nextCursor from the previous page"); noteId is self-evident. The description adds no parameter-level detail beyond what the schema states, so 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?

Specific verb ("List") plus resource ("a note's saved versions") and an ordering guarantee ("newest first"). It clearly reads as a version-history listing distinct from get_note or append_to_note, though it never names a sibling to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: you call it when you want a note's version history. There is no explicit when-to-use or when-not-to-use guidance, and no pointer telling the agent to follow up with get_note_version or restore_note_version once a version is identified.

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