Skip to main content
Glama

Change history for a subject

history
Read-only

Retrieve a subject's full change-log—oldest to newest values and statuses—to compare past and current stored facts.

Instructions

The change-log for a subject — every value it has held, oldest → newest, with status. The 'what did we use first vs now' view that additive stores can't give you. The subject is the key shown by list_memories.

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

Input Schema

NameRequiredDescriptionDefault
run_idNo
subjectYes
user_idNodefault
agent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

B3.1/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 the safety profile is covered. The description adds real value with ordering guarantees (oldest → newest) and the presence of a status field per entry. It says nothing about result size, pagination, or whether history is unbounded, which matters for a change-log that can grow indefinitely.

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 the definition and ordering guarantee before the framing sentence. The 'additive stores can't give you' clause is mildly promotional but still conveys the differentiating capability.

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 shape needn't be explained. However, with 0% schema coverage on three of four parameters and no mention of result limits, the description is insufficient for an agent to know how history is scoped by user or agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, so the description carries the full burden. It explains only `subject` (the key shown by `list_memories`) and leaves `run_id`, `user_id`, and `agent_id` entirely undefined in both schema and description, leaving scoping behavior unknowable.

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 shape: 'The change-log for a subject — every value it has held, oldest → newest, with status.' This clearly separates it from a current-value getter and from listing tools, and it ties `subject` back to `list_memories`. It doesn't explicitly name the current-value sibling, so it stops short of full disambiguation.

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 what did we use first vs now view that additive stores can't give you' frames the use case as temporal evolution, which implies when to reach for it. There is no explicit when-not guidance or named alternative for retrieving the current value, so routing is inferred rather than stated.

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