List active (unresolved) failures for this account, the current 'do not repeat' set.
| Name | Required | Description | Default |
|---|---|---|---|
| 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?
With no annotations provided, the description carries the burden of behavioral disclosure. It does convey that the tool returns only unresolved failures and frames them as the current 'do not repeat' set, but it does not mention read-only behavior, ordering, pagination, or response shape. This is adequate but not rich for a no-annotation tool.
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 a single, front-loaded sentence with no filler. Every part adds meaning: the verb, the filtered status, the account scope, and the 'do not repeat' semantic.
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 simple list tool with one optional parameter and a fully documented schema, the description covers the essential semantics well. The only gap is that with no output schema, return-value structure is not described, but the name and phrasing make the purpose sufficiently clear.
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%, and the single optional parameter is already well documented in the input schema. The description adds 'for this account' context, but it does not significantly extend what the schema already explains, so the baseline of 3 applies.
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 ('List') and resource ('failures'), and clarifies scope as 'active (unresolved)' and 'current do not repeat set.' This distinguishes it clearly from sibling tools like wyrm_failure_record, wyrm_failure_resolve, and wyrm_failure_check.
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 makes the tool's purpose clear, so when an agent needs to see active failures the usage is implied. However, it does not explicitly state when to prefer this tool over wyrm_failure_check, nor does it mention any alternatives or exclusions.
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.
