Skip to main content
Glama

Wyrm

by lk.ghosts.wyrm.mcp
OverviewDiscussionsAdmin

wyrm_quest_complete

Mark a quest completed, by its exact id (quest_id) or by matching the start of its title.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNothe quest title (or a unique prefix)
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
matchedYes
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "matched": {
+      "type": "integer"
+    },
+    "selector": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "selector",
+    "matched"
+  ],
+  "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

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation is a state change ('mark completed') but says nothing about permissions, reversibility, or what happens when a title prefix matches multiple quests — a real ambiguity risk given prefix matching.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight sentence, front-loaded with the action and the two targeting options; nothing extraneous. Slightly terse given the mutation semantics that remain unexplained, but structurally clean.

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 need not be described. However, for a no-annotation mutation tool, the description omits ambiguity handling and side-effect details, leaving it only minimally complete.

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 description coverage is 100%, so the schema already documents title, quest_id, and workspace. The description restates the id-vs-prefix distinction but adds no syntax or format details beyond what the schema provides, so baseline 3 applies.

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?

Specific verb ('Mark ... completed') plus resource ('quest') and the two identification modes. An agent knows what the tool does, but the description doesn't explicitly contrast it with sibling wyrm_quest_update, which also mutates quests.

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?

It explains the two ways to target a quest (exact quest_id or title prefix), which implies usage, but gives no explicit when-to-use/when-not guidance or alternatives such as wyrm_quest_update for non-completion changes.

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