Wyrm

wyrm_recall

Recall relevant memory artifacts (lessons, patterns, reasoning traces) for the current task. Hybrid semantic + full-text ranking — finds conceptually related memory, not just keyword matches.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Default 10, at most 50
`query`	Yes	Describe the current task or problem
`workspace`	No	Project/workspace to scope to (defaults to this connection's workspace; isolates work streams within your account)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`receipt`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "query": {
+      "type": "string"
+    },
+    "receipt": {
+      "properties": {
+        "memories": {
+          "type": "integer"
+        },
+        "note": {
+          "type": "string"
+        },
+        "ranking": {
+          "enum": [
+            "hybrid",
+            "fts_only"
+          ],
+          "type": "string"
+        },
+        "vectors_indexed": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "ranking",
+        "note"
+      ],
+      "type": "object"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "outcome": {
+            "type": "string"
+          },
+          "problem": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "integer"
+          },
+          "solution": {
+            "type": "string"
+          },
+          "why": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "rank",
+          "id",
+          "kind",
+          "problem"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results",
+    "receipt"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 14, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Default 10, at most 50"
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
First observedSep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully explains the hybrid semantic + full-text ranking mechanism, which is real behavioral context, but omits that this is a read-only operation, any permission/scoping caveats, or latency/limit behavior beyond what the schema states.

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 tight sentences with the core purpose front-loaded and the ranking behavior as supporting detail. Every clause earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need not be explained, and all parameters are covered by the schema. The description adequately conveys what the tool retrieves, though for an unannotated tool it could say more about safety and scoping behavior.

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 three parameters (query, limit, workspace) are already documented. The description adds 'for the current task' as framing for the query parameter but no syntax, format, or default detail beyond the schema, so baseline 3 is appropriate.

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 (Recall) and resource (memory artifacts, enumerated as lessons, patterns, reasoning traces) scoped to the current task. The phrase 'not just keyword matches' implicitly contrasts it with the keyword-oriented wyrm_search sibling, but never names it, so differentiation is suggestive rather than explicit.

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 description implies usage context ('for the current task', 'conceptually related memory') which suggests reaching for this when semantic recall is needed, but it never states when to prefer it over wyrm_search or wyrm_context_build/session_prime. The guidance is inferable rather than directive.

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

All Wyrm 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?