Skip to main content
Glama
Sign In
ctxvault

ctxvault

by Filippo-Venturini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

episode_history

Retrieve every version of a stored statement, oldest first, to trace how a belief changed or review what an episode said before a correction.

Instructions

Show every version of a statement, oldest first. Use this to explain why the vault believes something, or to see what an episode used to say before it was corrected.

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": {
      "vault_name": "<vault_name>",
      "episode_id": "<episode_id>"
    },
    "name": "episode_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
episode_idYes
vault_nameYes

Output Schema

NameRequiredDescriptionDefault
chainYes
episode_idYes
vault_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does add real behavioral information beyond the schema: results are chronological and prior versions survive corrections. However, it never states that the operation is non-mutating, what happens for an unknown episode_id, or whether long histories are paginated or truncated.

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?

Two sentences, zero filler. The output shape (all versions, oldest first) is front-loaded before the use-case sentence, which is the right order for an agent scanning for relevance.

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?

An output schema exists, so return-value explanation is rightly omitted, and the tool's core behavior is simple. What is missing is parameter-level orientation and error/edge-case behavior, which matters here because history tools are typically reached for in ambiguous debugging situations.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for both parameters and does not mention vault_name or episode_id at all. The names are largely self-explanatory, but an agent gets no clarification on whether episode_id is a UUID, slug, or how 'statement' relates to 'episode'.

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 verb and resource ('Show every version of a statement') plus the ordering guarantee ('oldest first'), which tells an agent exactly what comes back. It is distinguishable from mutating siblings like revise_episode or supersede_episode, but never names a contrasting read sibling (e.g. query_episodes) that would make the boundary explicit.

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 when-to-use scenarios: auditing the provenance of a belief and recovering a pre-correction version of an episode. There is no when-not guidance and no named alternative for 'I want the current value instead,' which is the most likely confusion against query_episodes.

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