Skip to main content
Glama
Sign In
Helios

Helios

by brazaoo4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

recall_history

Read-onlyIdempotent

Retrieve superseded and archived memory records by scope to audit config history, trace slot lineage, and debug past states. Returns read-only entries with validity timestamps and superseding IDs.

Instructions

Retrieve superseded and archived memory records for a scope to audit configuration history and slot lineage. Read-only: resolves scope aliases and returns up to limit (1-25) historical entries ordered by valid_to descending, including validity timestamps and superseding memory IDs. Use recall_history for time-travel debugging or reviewing retired facts; use recall_memories instead to search current active or [STALE] memories.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recall_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of historical records to return (capped at 25).
scopeNoProject, repository, or directory name to retrieve historical audit trail for.global

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.3

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description then adds real behavioral context: scope aliases are resolved, results are ordered by valid_to descending, and each entry carries validity timestamps and superseding memory IDs. It omits edge behavior (e.g., unknown scope returning empty vs. error), which is why this is not 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?

Three tight sentences: purpose first, operational behavior second, tool selection third. No filler, and the most decision-relevant routing information is present without burying the primary action.

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?

An output schema exists, so return-value structure needn't be explained; the description still conveys ordering and included fields. For a two-parameter read-only tool with full schema coverage, nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, but the description adds meaning beyond the schema: it explains that scope is alias-resolved and reinforces the 1-25 cap on limit. That alias resolution detail is genuinely non-obvious from the parameter description alone.

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 ('Retrieve superseded and archived memory records for a scope') plus an explicit purpose (auditing configuration history and slot lineage). This is clearly distinct from the sibling recall_memories, which the description names directly.

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

Usage Guidelines5/5

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

Explicitly names the alternative ('use recall_memories instead to search current active or [STALE] memories') and gives concrete triggering scenarios ('time-travel debugging or reviewing retired facts'). Both the when and the when-not are covered.

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