Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

List a note's versions

get_note_history
Read-onlyIdempotent

List a Note's versions, newest first, a page at a time: the current one (is_current) and earlier ones, kept for 90 days after they were replaced (some longer). Each has its id (the version_id of get_note_version and restore_note_version), revision, accepted_at and expires_at; oldest_available_at says how far back history reaches, can_restore whether you may restore one. Use it to see what a Note said before or to undo an edit; get_note reads the current content.

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": {
      "note_id": "<note_id>"
    },
    "name": "get_note_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor from the previous page; omit for the first page.
note_idYesA Note's id, from get_thread, search or get_note.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantial extra context: 90-day retention with exceptions, the fields each version carries, and the can_restore/oldest_available_at flags that determine what the agent can act on.

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?

Front-loads the action and ordering, then the returned fields, then the use case and alternative. Dense but every clause carries information; the field enumeration in one sentence is slightly heavy but justified given no output schema.

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 compensates by enumerating returned fields and their semantics (is_current, revision, accepted_at, expires_at, can_restore, oldest_available_at). Nothing needed to call or interpret the result is missing.

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% and both parameters are documented there, so baseline is 3; the description adds meaning by tying version 'id' to the version_id consumed by get_note_version and restore_note_version, and clarifying the paged cursor model.

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 and resource ('List a Note's versions') plus ordering ('newest first') and pagination mode, and explicitly separates itself from get_note ('get_note reads the current content') and links to get_note_version/restore_note_version via version_id.

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 concrete use cases ('see what a Note said before or to undo an edit') and names the sibling to use instead for current content. It stops short of explicit when-not conditions such as retention expiry handling, but the routing guidance is clear.

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

All ThreadPage toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources