Skip to main content
Glama

ctxstore — memory that follows you across models

Fact Version History

get_fact_history
Read-onlyIdempotent

Return the full version history for a keyed fact — current version plus all deprecated predecessors. Use to see how a fact evolved over time or to undo an accidental correction. Returns list of fact versions ordered newest → oldest.

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": {
      "key": "<key>"
    },
    "name": "get_fact_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe fact key to retrieve history for (e.g. 'session-latest', 'current-stack')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds behavior beyond them: the result includes deprecated predecessors, not just the live version, and is ordered newest to oldest — details an agent could not infer from annotations.

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?

Three short sentences, front-loaded with what is returned and then when to use it. Slight redundancy between 'current version plus all deprecated predecessors' and 'list of fact versions ordered newest → oldest', but both clauses add distinct information (contents vs. ordering).

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 tool with no output schema, the description covers return contents and ordering, which is the essential missing piece. It omits edge-case behavior such as an unknown key or a fact with no history, but that gap is minor for this complexity level.

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 only parameter's description already includes example keys ('session-latest', 'current-stack'). The description adds nothing further about the key parameter, so the schema carries the full burden and baseline 3 applies.

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 ('return the full version history for a keyed fact') and scopes it precisely as current version plus all deprecated predecessors. This distinguishes it from the sibling get_fact (current value only) and search_facts without opening any schema.

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 two concrete use cases: seeing how a fact evolved over time, and undoing an accidental correction. That is clear situational guidance, but it does not explicitly name the alternative tool (e.g. get_fact) for retrieving only the current value, leaving that routing to inference.

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.