List secret NAMES (and non-secret hints) in this account's vault. Never returns secret values.
| 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?
No annotations are provided, so the description carries the behavioral burden. It adds a clear, non-obvious guarantee that secret values are never returned, and clarifies the output category. It does not mention pagination, errors, or side effects, but 'List' implies a read-only operation and the return scope is described.
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?
One information-dense sentence, with the primary action and resource front-loaded and the important negative guarantee in a short follow-up. There is no redundant wording.
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 no output schema, the description adequately explains what is returned (names and non-secret hints) and what is never returned (secret values). The workspace behavior is covered by the schema, so nothing critical is missing.
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% for the single optional parameter, workspace, and the schema already explains its default and purpose. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate.
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 a specific resource ('secret NAMES... in this account's vault'). It also explicitly states 'Never returns secret values', which distinguishes it from vault_get and other vault tools.
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?
It gives clear context for the listing use case: you call this to get secret names and non-secret hints. The 'Never returns secret values' statement is a useful exclusion, telling an agent not to use this tool when it needs actual secret values, though it does not name vault_get explicitly.
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.
