Skip to main content
Glama

Note history

note_history
Read-only

The versions a note's text was kept in, newest first (update_note keeps one before every rewrite). Pass version to read that version's text as Markdown.

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": "<note>"
    },
    "name": "note_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesThe note. Its id (from any other tool's output) or its exact title.
versionNoA version id from the list, to read its text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Read-only semantics are already covered by the annotations, but the description adds useful context: newest-first ordering, the retention rule tied to update_note, and the fact that passing version returns Markdown text. It doesn't mention pagination, limits on how many versions are kept, or what metadata accompanies each entry, so the list-case behavior remains partly opaque.

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?

Two compact sentences with no filler, and the core value (the version list, newest first) is front-loaded. The parenthetical efficiently explains the origin of the data.

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?

With no output schema, the description still conveys return ordering and format for the version-detail case, which covers the essentials for a two-parameter read tool. It could say a bit more about what each list entry contains, but nothing critical to correct invocation is missing.

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 the schema already documents both note and version, and the baseline of 3 applies. The description adds only the Markdown output detail for the version parameter, not new syntax or format information for the note parameter.

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 names the specific resource (the historical versions of a note's text) and states the ordering (newest first), which separates it from siblings like read_note or list_notes. The one gap is that it never uses an explicit verb for the base call, though the intent is still clear.

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?

It states what the optional version parameter is for and mentions that update_note creates entries, which gives implied context for when to reach for this tool. It never explicitly says when to use this versus read_note or restore_note_version.

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.

Resources