Skip to main content
Glama

history

Read-only

Retrieve all versions of a fact, from oldest to current, using any version's memory ID to inspect how information changed over time.

Instructions

Todas las versiones de un hecho, de la más antigua a la vigente.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYesId de cualquier versión del hecho.

Output Schema

NameRequiredDescriptionDefault
versionsYesDe la más antigua a la vigente

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description's genuine addition is the ordering guarantee (oldest to current), which tells the agent how to interpret the returned array, but it does not say whether superseded or deleted versions are included or how long history is retained.

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?

A single economical sentence with the ordering information front-loaded and no filler. It is arguably too terse to carry any usage signal, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return-value shape need not be explained, and the ordering note covers the key interpretation question. Still, for a version-history tool the description leaves open what a version is in this store and whether gaps or deletions appear in the sequence.

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?

Only one parameter, and the schema fully documents it at 100% coverage, including the useful note that the id may be of any version of the fact. The description adds nothing beyond that, so the baseline of 3 applies.

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?

States a specific resource and scope: all versions of a fact, ordered oldest to current. That distinguishes it from siblings like recall (current value) or forget/supersede (mutations), though the retrieval verb itself is only implied rather than named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what it returns but never when to use it instead of recall or list_memories, nor any prerequisite such as needing a memory_id from a prior lookup. Usage is inferable from the name alone.

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

Deploy Server

Other Tools