Skip to main content
Glama

Recall from current memory

recall
Read-only

Answers questions from active memory only, returning 'I don't know' instead of guessing and never using retired facts; enable history only for past-state or switch questions.

Instructions

Answer a question from CURRENT memory — the active value ('what state library do we use?') or a multi-hop question over current facts. Returns 'I don't know' rather than guessing, and NEVER answers from a retired/retracted fact. For the timeline of a subject, use history.

Set include_history=True ONLY for questions explicitly about the past — 'what did we use before?', 'when did we switch?' — where retired facts are the answer. It is off by default because with it off, superseded values are never loaded at all, so a stale value cannot be returned as current regardless of how the model behaves. Leaving it off is the guarantee; turning it on trades that for reach into the timeline.

critical_categories (comma-separated) names fact categories that must ALWAYS reach the answer regardless of ranking — 'allergy,active_medication' in a clinical deployment. Ordinary recall is semantic top-k, so a fact that does not rank is invisible, not merely deprioritised; for some categories that is a safety failure rather than a quality one. Leave empty to use the deployment-wide VAYL_CRITICAL_CATEGORIES; an empty value never means 'none'.

Set explain=True to also get the PROVENANCE — the exact facts used to answer, each with who asserted it, its confidence, and what it superseded. That's the truthful basis for an audit of why the agent believes what it does (and it's what record_decision snapshots).

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": {
      "question": "<question>"
    },
    "name": "recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
explainNo
user_idNodefault
agent_idNo
questionYes
include_historyNo
critical_categoriesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavioral context — refusal ('I don't know') instead of guessing, the mechanical guarantee that superseded values are never loaded when include_history is off, and that critical_categories bypasses semantic top-k so unranked facts are invisible rather than deprioritised. Those are exactly the non-obvious traits annotations cannot express, so this sits well above the annotation baseline.

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?

Front-loaded with the core behavior and the sibling contrast, then one paragraph per non-obvious parameter. Dense but nearly every sentence carries a fact an agent could not infer; the critical_categories paragraph is the longest and could be tightened without losing meaning.

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 shape needn't be described, and the remaining burden — refusal behavior, safety default, category-pinning, audit provenance — is fully covered. What an agent needs to call this correctly and interpret the result is present.

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?

Schema description coverage is 0%, so the description must carry the load; it thoroughly explains include_history (default, safety trade-off), critical_categories (comma-separated, empty falls back to deployment-wide VAYL_CRITICAL_CATEGORIES, empty never means 'none'), and explain (provenance payload contents). It leaves run_id, user_id, and agent_id unmentioned, so three of seven parameters have no semantics anywhere.

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+resource: answer a question from CURRENT memory, including the multi-hop case, and explicitly names the sibling (`history`) that serves a different need. The scope qualifier 'current' is defined operationally (active value, never a retired fact).

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?

Gives explicit routing rules and exclusions: use `history` for a timeline, set `include_history=True` ONLY for past-oriented questions, use `explain=True` when provenance/audit basis is needed. Each recommendation pairs a condition with the alternative it selects against.

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