Skip to main content
Glama

Get earlier versions of a record

get_history
Read-onlyIdempotent

List what a software record, request or proposal said before each edit. USE WHEN a record's version is above 1 and the user asks what changed, or you need the text a verdict, proposal or earlier answer was based on. NEEDS entity_type and entity_id. NO side effects; public. Returns current_version and earlier_versions (newest first) with their content, when each was published and replaced, and the author's change note. Only the current record is in force. Recovery: NOT_FOUND means the record does not exist or is no longer public.

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": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>"
    },
    "name": "get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesID of the record: sw_... (or slug), req_... or sol_....
entity_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With readOnly/idempotent/destructive hints already supplied, the description still adds real value: it declares the record is public, states the return shape (current_version plus earlier_versions newest-first, with content, publish/replace timestamps, and the author's change note) because no output schema exists, and documents a NOT_FOUND recovery path. The 'NO side effects' clause partly restates the annotations, keeping it from a 5.

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?

Front-loaded with the core statement, then telegraphically segmented USE WHEN / NEEDS / returns / Recovery blocks. Every sentence carries either a trigger, a prerequisite, a return detail, or an error case; nothing is filler.

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?

For a two-parameter read tool with no output schema, the definition covers input prerequisites, return contents and ordering, semantic caveat about which version is in force, and the primary error state. An agent has everything needed to call it and interpret the result.

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 50%: entity_id is described in the schema, entity_type is not. The description only says it 'NEEDS entity_type and entity_id' and loosely maps the accepted types ('software record, request or proposal'), without spelling out the enum values software/request/solution or how they select behavior. Minimal compensation for the coverage gap.

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?

Opens with a specific verb+resource: 'List what a software record, request or proposal said before each edit.' An agent can immediately distinguish this versioning-history read from siblings like get_software or get_request, which return the current record only.

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?

'USE WHEN a record's version is above 1 and the user asks what changed, or you need the text a verdict, proposal or earlier answer was based on' gives concrete trigger conditions, and 'Only the current record is in force' implies the boundary with the current-record getters. However, no sibling is named as an explicit alternative or exclusion, so it falls short of a 5.

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