Trace decisions. Pass truth ('category.key') to see which decisions depend on it (what to revisit when it changes); pass nothing to list recent decisions and what they rest on.
| Name | Required | Description | Default |
|---|---|---|---|
| truth | No | a truth ref 'category.key' to find dependents of | |
| workspace | No | Project/workspace to scope to (defaults to this connection's workspace; isolates work streams within your account) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the two modes and their expected outcomes, which is useful. However, with no annotations provided, it does not explicitly state that the tool is read-only or has no side effects, leaving some of that burden unmet.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The core action is front-loaded, and the dual-mode behavior is packed into a single well-structured sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the two invocation modes and gives a broad sense of the return information, which is enough to call the tool for many cases. However, it lacks output format details, a definition of 'recent', and any clarification of how this tool relates to the decision-specific sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents both parameters fully, and the description adds meaningful context by explaining what passing 'truth' accomplishes ('what to revisit when it changes') and what happens when it is omitted. The workspace parameter is not expanded, but the schema covers it adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('trace decisions') and defines two concrete modes: finding dependents of a truth and listing recent decisions with their foundations. However, it does not explicitly distinguish itself from sibling tools like wyrm_decision_upstream or wyrm_decision_downstream, so it falls short of a perfect 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear, direct usage context: pass 'truth' to find dependents, pass nothing to list recent decisions. It does not mention when to prefer a sibling tool instead, but the invocation branches are explicit and unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have heavily overlapping purposes: wyrm_all_quests vs wyrm_quest_list, wyrm_decision_downstream vs wyrm_decision_trace, and wyrm_recall vs wyrm_search are near-duplicates in behavior. wyrm_capture also overlaps with wyrm_remember, wyrm_truth_set, wyrm_quest_add, and wyrm_decided_because, making it hard for an agent to reliably pick the right tool.
Most names share the wyrm_ prefix and many follow a resource-action pattern like truth_set, quest_list, and failure_record. However, the pattern is broken by names like wyrm_all_quests, wyrm_decided_because, wyrm_context_build, wyrm_remember, and wyrm_capture, mixing noun-first, verb-first, and non-patterned names.
At 31 tools this is above the heavy threshold, and several tools appear redundant or mergeable, such as wyrm_all_quests/quest_list, decision_trace/downstream, capture/remember, and context_build/session_prime. The breadth is real, but the count feels inflated by overlapping entry points rather than distinct capabilities.
The tool surface covers core lifecycles well: quests have add/claim/update/complete/release, failures have record/check/list/resolve, decisions have record/trace/invalidate, and the vault has full get/put/list/delete. The main gaps are the lack of delete/update for memory artifacts and ground truths, and no explicit way to remove stale artifacts.
