Show the ground truths a decision rests on (its upstream dependencies) with each truth's CURRENT value — so you can tell whether the basis still holds. Match by decision title prefix.
| Name | Required | Description | Default |
|---|---|---|---|
| decision | Yes | the decision text (or a unique prefix) | |
| 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?
No annotations are provided, so the description carries the transparency burden. It discloses a key behavioral trait: values are CURRENT, not historical, and matching is by decision title prefix. However, it does not state whether the operation is strictly read-only, what happens on no match or ambiguous prefix, or precisely how results are structured.
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?
The description is one tight sentence that front-loads the core action, then adds the current-value purpose and the matching behavior. No words are wasted and every clause contributes useful information.
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?
For a straightforward two-parameter query tool, the description covers what it returns (ground truths with current values), why it is useful, and how arguments are matched. It lacks an explicit note about empty results or prefix ambiguity, but those are minor given the tool's simplicity and high schema coverage.
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?
Schema description coverage is 100%, so the schema already explains both parameters. The description adds little beyond the schema's own 'unique prefix' wording, though it reinforces the prefix-matching behavior. This meets the baseline but does not elevate it.
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 uses a specific verb and resource: 'Show the ground truths a decision rests on (its upstream dependencies)' with current values. It clearly distinguishes itself from the sibling wyrm_decision_downstream by focusing on 'upstream.' The prefix-matching instruction adds operational clarity.
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 phrase 'so you can tell whether the basis still holds' provides clear context for when to use the tool: when checking whether a decision's founding assumptions remain valid. It does not explicitly name alternatives or exclusions, but the upstream/downstream contrast with sibling tools makes the intended use reasonably clear.
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.
