Skip to main content
Glama
Sign In

Wyrm

by lk.ghosts.wyrm.mcp
OverviewDiscussionsAdmin

wyrm_quest_claim

Claim an open quest (multi-agent coordination) so others know it's being worked. Matches by exact id (quest_id) or title prefix. Refuses if already claimed by someone else unless force is set.

Input Schema

NameRequiredDescriptionDefault
byNoclaimant label (agent/person); defaults to 'agent'
forceNo
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

NameRequiredDescriptionDefault
byYes
noteNo
titleNo
claimedYes
quest_idNo
selectorYes
claimed_byNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "by": {
+      "type": "string"
+    },
+    "claimed": {
+      "type": "boolean"
+    },
+    "claimed_by": {
+      "type": "string"
+    },
+    "quest_id": {
+      "type": "string"
+    },
+    "selector": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "selector",
+    "claimed",
+    "by"
+  ],
+  "type": "object"
+}
  3. 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: +[]
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description must carry the behavioral load, and it does disclose the key failure mode ('Refuses if already claimed by someone else') and the override ('unless `force` is set'). It does not address concurrency/atomicity of the claim, what happens on ambiguous title-prefix matches, or side effects beyond the claim marker.

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?

Three short sentences, front-loaded with the action and rationale before matching modes and the refusal rule. Every clause carries information an agent needs; nothing is padding.

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

Completeness4/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 needn't be explained. For an unannotated mutation tool, the description covers purpose, matching, and the refusal/override rule; only edge cases like ambiguous prefix matches and non-idempotency remain undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, and the description compensates for the biggest gaps: it explains force as the override for a conflicting claim and defines title as a prefix match (a semantic the schema does not state). quest_id's exact-match guidance and the 'by' default are already in the schema, so there is some redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (claim) and resource (an open quest), plus the motivation ('so others know it's being worked') and the multi-agent coordination scope. An agent can immediately distinguish this from wyrm_quest_release, wyrm_quest_complete, and wyrm_quest_add without opening any schema.

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

Usage Guidelines4/5

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

Explains the usage context clearly (coordination with other agents) and gives selection guidance between the two lookup modes: exact id via quest_id or a title prefix. It doesn't name sibling tools as alternatives or say when not to claim, so it stops short of full routing guidance.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources