WhiteMagic — governed local memory for agent continuity

Hybrid Recall

memory.hybrid_recall

Read-onlyIdempotent

Compatibility alias of memory.search with BM25 + dense vector fusion.

Input Schema

Name	Required	Description
`limit`	No	Maximum results (default: 10)
`query`	Yes	Search query terms
`since`	No	Inclusive lower time bound: RFC3339 or epoch seconds
`until`	No	Inclusive upper time bound: RFC3339 or epoch seconds
`galaxy`	No	Galaxy filter (default: all)
`min_score`	No	Absolute BM25 score floor
`min_trust`	No	Minimum source_trust (0-1)
`time_basis`	No	Time basis for since/until: 'recorded' or 'event'
`include_cold`	No	Opt-in unranked cold recovery
`min_importance`	No	Minimum memory importance (0-1)
`cold_scan_limit`	No	Maximum cold records to scan when include_cold is set (default 2048)
`min_score_ratio`	No	Relative floor: reject hits below this fraction of the top score

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 22, 2026

changedInput schema / properties / galaxy / description

Previous value: -"Galaxy filter (optional; default: search all memory galaxies, results labeled; \"all\" is accepted as an alias for the unfiltered default)"New value: +"Galaxy filter (default: all)"

changedInput schema / properties / include_cold / description

Previous value: -"Opt-in unranked cold recovery (no thaw). Trust/importance floors apply; BM25 floors do not apply to unscored recovery. Search content is scrubbed navigation capped at 8192 characters; read by id/galaxy for the exact original."New value: +"Opt-in unranked cold recovery"

changedInput schema / properties / limit / description

Previous value: -"Maximum results (default 10; must be >= 1)"New value: +"Maximum results (default: 10)"

removedInput schema / properties / limit / minimum
```
Removed value: -1
```

changedInput schema / properties / min_trust / description

Previous value: -"Minimum source_trust (0-1): drop results below this trust floor"New value: +"Minimum source_trust (0-1)"

changedInput schema / properties / query / description

Previous value: -"Full-text query"New value: +"Search query terms"

changedInput schema / properties / since / description

Previous value: -"Inclusive lower time bound: RFC3339 ('2026-02-01T00:00:00Z') or epoch seconds"New value: +"Inclusive lower time bound: RFC3339 or epoch seconds"

changedInput schema / properties / time_basis / description

Previous value: -"Time basis for since/until: 'recorded' (created_at, default) or 'event' (event_time, falling back to created_at when unset)"New value: +"Time basis for since/until: 'recorded' or 'event'"

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "description": "Recall results (memory.search implementation) with an evidence bundle and recall-mode disclosure.",
-  "properties": {
-    "count": {
-      "description": "Number of results returned",
-      "type": "integer"
-    },
-    "evidence_bundle": {
-      "description": "Per-result provenance (coverage, history, integrity, retrieval, source_time, visibility) plus conflicts.",
-      "type": "object"
-    },
-    "galaxy": {
-      "description": "Galaxy scope the query ran against",
-      "type": "string"
-    },
-    "hint": {
-      "description": "Optional recovery hint when results are thin (null when there is none)",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "recall_mode": {
-      "description": "Retrieval path used (hybrid, episodic, fts, importance, none)",
-      "type": "string"
-    },
-    "results": {
-      "description": "Ranked memories with per-result source labels",
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "status": {
-      "description": "Operation status",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedOct 18, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed3 schema fields changedOct 1, 2026

addedInput schema / properties / since

Added value: +{
+  "description": "Inclusive lower time bound: RFC3339 ('2026-02-01T00:00:00Z') or epoch seconds",
+  "type": "string"
+}

addedInput schema / properties / time_basis

Added value: +{
+  "description": "Time basis for since/until: 'recorded' (created_at, default) or 'event' (event_time, falling back to created_at when unset)",
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "Inclusive upper time bound: RFC3339 or epoch seconds",
+  "type": "string"
+}

Changed3 schema fields changedSep 28, 2026

changedOutput schema / description

Previous value: -"Fused recall results with an evidence bundle and recall-mode disclosure."New value: +"Recall results (memory.search implementation) with an evidence bundle and recall-mode disclosure."

changedOutput schema / properties / hint / description

Previous value: -"Optional recovery hint when results are thin"New value: +"Optional recovery hint when results are thin (null when there is none)"

changedOutput schema / properties / hint / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed2 schema fields changedSep 24, 2026

changedOutput schema / description

Previous value: -"Result envelope for this tool; fields vary by operation."New value: +"Fused recall results with an evidence bundle and recall-mode disclosure."

addedOutput schema / properties

Added value: +{
+  "count": {
+    "description": "Number of results returned",
+    "type": "integer"
+  },
+  "evidence_bundle": {
+    "description": "Per-result provenance (coverage, history, integrity, retrieval, source_time, visibility) plus conflicts.",
+    "type": "object"
+  },
+  "galaxy": {
+    "description": "Galaxy scope the query ran against",
+    "type": "string"
+  },
+  "hint": {
+    "description": "Optional recovery hint when results are thin",
+    "type": "string"
+  },
+  "recall_mode": {
+    "description": "Retrieval path used (hybrid, episodic, fts, importance, none)",
+    "type": "string"
+  },
+  "results": {
+    "description": "Ranked memories with per-result source labels",
+    "items": {
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "status": {
+    "description": "Operation status",
+    "type": "string"
+  }
+}

First observedSep 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that results come from hybrid BM25/dense fusion and that this is an alias, but it does not mention return format, pagination, scoring behavior, or cold-recovery semantics.

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?

The description is a single front-loaded sentence with no filler. Every word serves to identify the alias relationship and fusion method.

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?

With 12 parameters, no output schema, and rich annotations/schema descriptions, the description is minimal. It covers the alias and fusion nature but leaves the agent to infer return shape and practical selection guidance from memory.search or the schema.

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?

Schema description coverage is 100%, so all 12 parameters are already documented in the schema. The description adds no parameter-specific meaning beyond the schema, which is appropriate for this baseline.

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?

The description explicitly identifies the tool as a compatibility alias of memory.search and names the retrieval mechanism (BM25 + dense vector fusion). This makes the resource and method clear, though it does not spell out the action verb or when an agent should choose this alias over the canonical memory.search sibling.

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 phrase 'Compatibility alias' implies the tool exists for backward-compatibility scenarios, but the description never explicitly says when to use it versus memory.search or when to avoid it. Usage is only implied, not stated.

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

All WhiteMagic — governed local memory for agent continuity tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?