Wyrm

wyrm_session_prime

Load this account's working context at the start of a session: ground truths, open quests, active failures, and (if a focus is given) the most relevant memory. Call this first, the cloud equivalent of Claude Code's session rehydrate.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`focus`	No	optional current task/topic to bias the recall
`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
`focus`	No
`memory`	Yes
`quests`	Yes
`truths`	Yes
`failures`	Yes
`workspace`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "failures": {
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "scope": {
+            "type": "string"
+          },
+          "target": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "scope",
+          "target",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "focus": {
+      "type": "string"
+    },
+    "memory": {
+      "items": {
+        "properties": {
+          "kind": {
+            "type": "string"
+          },
+          "problem": {
+            "type": "string"
+          },
+          "solution": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "kind",
+          "problem"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "quests": {
+      "items": {
+        "properties": {
+          "priority": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "priority"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "truths": {
+      "items": {
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "key": {
+            "type": "string"
+          },
+          "value": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "category",
+          "key",
+          "value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "workspace": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "truths",
+    "quests",
+    "failures",
+    "memory"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Without annotations, the description carries the burden and does disclose the assembled contents and the conditional effect of 'focus' on memory recall. It implies a read-only load but does not explicitly address auth, side effects, or rate limits.

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 efficient sentences: the first states the purpose and contents, the second gives the priority directive. It is front-loaded and every clause earns its place.

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?

Complete for a session-bootstrap tool with a rich schema and an output schema that covers return values. The only missing context is explicit sibling differentiation and when-not guidance, which are minor for this use case.

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 both parameters are already well documented. The description reinforces their role in context assembly but adds no format or syntax detail beyond what the schema provides, making 3 the appropriate 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?

States a specific verb ('Load') and resource ('account's working context'), and enumerates what is included: ground truths, open quests, active failures, and relevant memory. It is clear but does not distinguish itself from siblings such as wyrm_session_rehydrate or wyrm_context_build.

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

Usage Guidelines4/5

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

Explicitly says 'Call this first' and anchors usage to 'the start of a session', which gives clear context. It does not state when not to use it or name a sibling alternative, so it falls short of full when/when-not guidance.

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?