WhiteMagic — governed local memory for agent continuity

WhiteMagic memory and continuity meta-tool

wm

Read-only

WhiteMagic meta-tool — memory and continuity kernel over the curated tool surface (70 tools): persistent memory, session continuity and recall, governance/audit, and local tool execution. Mode: READ-ONLY — writes (session.*, memory.create/update) are refused; recall only. Scope: store /srv/whitemagic/hosted-store/lmdb. Invoke with thought= (auto-routed), route= (e.g. 'memory.search', 'session.continuity'), or args= (passthrough). Provide exactly one of thought or route. Say 'list tools' to enumerate the curated surface. Prefer a discrete lifecycle tool when one matches your task; use wm for natural-language routing and the wider curated catalog.

Input Schema

TableJSON Schema

Name	Required	Description
`args`	No	Arguments to pass through to the target tool.
`route`	No	Explicit tool name for direct dispatch (e.g. 'memory.create', 'tools.list').
`thought`	No	Natural language input describing what to do. Auto-routes to the best-matching tool via TF-IDF NLU classification.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`_wm_route`	No	Dispatch metadata: resolved tool, routing confidence, matched input.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

changedOutput schema / description

Previous value: -"The dispatched tool's result envelope; fields vary by route."New value: +"The dispatched tool's result envelope plus `_wm_route` dispatch metadata; fields vary by route."

addedOutput schema / properties

Added value: +{
+  "_wm_route": {
+    "description": "Dispatch metadata: resolved tool, routing confidence, matched input.",
+    "properties": {
+      "confidence": {
+        "description": "Routing confidence (1.0 for explicit routes)",
+        "type": "number"
+      },
+      "input": {
+        "description": "Routing input that produced the match",
+        "type": "string"
+      },
+      "tool": {
+        "description": "Resolved route name",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+}

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the READ-ONLY mode statement and the concrete refusal behavior for session.* and memory.create/update writes, plus the storage scope path. That is genuine added context beyond annotations, though rate limits and routing failure behavior are not described.

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 meta-tool identity and capability areas, followed by mode, scope, and invocation syntax in a logical order. It is dense but every clause carries information; only the '70 tools' aside is arguably incidental.

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?

For a routing meta-tool with a rich output schema, the description covers mode, scope, all three invocation styles, the exclusivity constraint, enumeration, and the decision rule against discrete siblings. An agent has everything needed to call it correctly without opening the schema.

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 coverage is 100%, so baseline is 3, but the description adds real semantic value: examples of route values ('memory.search', 'session.continuity'), the auto-routing behavior of thought, the passthrough nature of args, and the exactly-one-of constraint that the schema does not encode.

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 names the resource (persistent memory, session continuity, governance/audit, local tool execution) and explicitly frames itself as a routing meta-tool, which distinguishes it from the discrete siblings listed. The phrase 'memory and continuity kernel' is somewhat jargon-heavy, but the following clause grounds it in concrete capability areas.

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?

It states exactly how to invoke (thought=, route=, args=), the mutual-exclusion rule ('provide exactly one of thought or route'), and when to prefer alternatives ('Prefer a discrete lifecycle tool when one matches your task; use wm for natural-language routing and the wider curated catalog'). It even documents the 'list tools' enumeration path.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?