Skip to main content
Glama

Post history

post_history
Read-only

The versions a published note's post went out in, newest first: what readers saw when, and the line written about each change. update_post with restore_version makes an earlier one current again.

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": "post_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesThe published note. Its id (from any other tool's output) or its exact title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the result shape and ordering ('newest first', 'what readers saw when, and the line written about each change'), which matters with no output schema. It does not disclose pagination or the behaviour for a note that was never published.

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?

Two sentences, front-loaded with what is returned and the ordering, and the follow-up action comes second. The phrasing is slightly ornate ('went out in') but no sentence is wasted.

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?

For a single-parameter read-only tool with full schema coverage, the description covers purpose, ordering, and return contents, which compensates for the absent output schema. Only edge-case behaviour (a note with no published post, or a non-published note) is undefined.

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% and the single 'note' parameter is already fully documented in the schema. The description adds only that the note must be published, a useful constraint beyond the schema, but nothing about id-vs-title resolution or failure modes. Baseline 3 is appropriate when the schema does the heavy lifting.

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 uses a specific resource and frames it clearly: 'the versions a published note's post went out in, newest first'. It scopes the tool to published notes and describes what each entry contains (what readers saw and the change line). It does not explicitly distinguish the tool from the sibling note_history, so the distinction from the note-level counterpart is left implicit.

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?

The second sentence points at a related action ('update_post with restore_version makes an earlier one current again'), implying that this tool is for reviewing history before restoring. However, it never states when to call this tool directly instead of note_history, and it names no exclusion or prerequisite. The guidance is implied rather than explicit.

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