Skip to main content
Glama

Wyrm

by lk.ghosts.wyrm.mcp
OverviewDiscussionsAdmin

wyrm_quest_release

Release a claimed quest so it's open for others again. Matches by exact id (quest_id) or title prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
quest_idNoExact quest id from wyrm_quest_add or wyrm_quest_list (questId and id are accepted too). Use instead of title.
workspaceNoProject/workspace to scope to (defaults to this connection's workspace; isolates work streams within your account)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
releasedYes
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "released": {
+      "type": "integer"
+    },
+    "selector": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "selector",
+    "released"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / quest_id
      Added value: +{
+  "description": "Exact quest id from wyrm_quest_add or wyrm_quest_list (questId and id are accepted too). Use instead of title.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "title"
-]New value: +[]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the matching behavior (exact id vs. title prefix), but omits key behavioral traits: whether the caller must be the one who claimed the quest, what happens if the quest was never claimed, and how ambiguity is handled when a title prefix matches multiple quests.

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 short sentences, front-loaded with the action and its effect, then the matching rule. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values are covered, but for an unannotated mutation tool the description leaves out preconditions and error/ambiguity behavior for a prefix match. Adequate to call the tool, but an agent cannot predict the failure modes.

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 coverage is 67% and the description adds real value by specifying that 'title' is matched by prefix, which the schema does not state. However, it does not resolve the more important ambiguity: all three parameters are optional, and the precedence rule when both title and quest_id are supplied is left to 'Use instead of title' in the schema rather than explained.

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 (release) and resource (a claimed quest) plus the resulting state change ('open for others again'), which cleanly distinguishes it from the imperative siblings wyrm_quest_claim and wyrm_quest_complete. It does not explicitly name those siblings, so it falls short of the 5 bar for sibling differentiation.

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

Usage Guidelines3/5

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

The phrase 'so it's open for others again' implies the scenario (undoing a claim you no longer need), but there is no explicit guidance on when to use this versus wyrm_quest_complete or wyrm_quest_update. No prerequisites or conditions are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wyrm toolsInspect
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