create_quest_mnemonsCreate Quest mnemons. questStatus is one of active|completed|failed. Players may not call this — GM/co-GM only.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| campaignId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / items / items / properties / blocksRemoved value: -{
- "description": "Initial content blocks (at least one).",
- "items": {
- "additionalProperties": false,
- "description": "A single content block. Image blocks need assetId OR (data + mimeType).",
- "properties": {
- "assetId": {
- "description": "Image block: pre-uploaded campaign asset id.",
- "type": "string"
- },
- "caption": {
- "description": "Image block caption.",
- "type": "string"
- },
- "checked": {
- "description": "Todo-block checked state.",
- "type": "boolean"
- },
- "content": {
- "description": "HTML text content for text-type blocks. Use <b>/<i>/<u>/<a>/<br>/<img> — NOT Markdown.",
- "type": "string"
- },
- "data": {
- "description": "Image block: inline base64 data (decoded server-side, max 5MB).",
- "type": "string"
- },
- "filename": {
- "description": "Image block filename hint.",
- "type": "string"
- },
- "language": {
- "description": "Code-block language hint.",
- "type": "string"
- },
- "mimeType": {
- "description": "Image block mime type — required when 'data' is set.",
- "type": "string"
- },
- "type": {
- "description": "Block type.",
- "enum": [
- "paragraph",
- "heading1",
- "heading2",
- "bullet_list",
- "numbered_list",
- "todo",
- "quote",
- "code",
- "callout",
- "divider",
- "image"
- ],
- "type": "string"
- }
- },
- "required": [
- "type"
- ],
- "type": "object"
- },
- "minItems": 1,
- "type": "array"
-}Input schema / properties / items / items / properties / markdownAdded value: +{
+ "description": "Body content as Markdown. Mentions: @[label](mnemon:<entryId>). Images:  — upload the asset first.",
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / items / items / requiredPrevious value: -[
- "title",
- "blocks"
-]New value: +[
+ "title",
+ "markdown"
+]Input schema / properties / items / items / properties / rewardsAdded value: +{
+ "description": "Rewards shown when the quest completes.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "amount": {
+ "description": "Numeric amount for stack-like rewards.",
+ "type": "integer"
+ },
+ "itemId": {
+ "description": "Optional reference to an item entry.",
+ "type": "string"
+ },
+ "label": {
+ "description": "Display label (e.g. '100 gp', 'Ancient map').",
+ "type": "string"
+ },
+ "linkedStepIds": {
+ "description": "stepIds and/or subquest entry ids whose completion unlocks this reward.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "notes": {
+ "type": "string"
+ },
+ "rewardType": {
+ "description": "Bucket: Gold | Item | XP | Reputation | etc.",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+}Input schema / properties / items / items / properties / stepsAdded value: +{
+ "description": "Ordered list of quest steps. Omit to leave empty.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "description": {
+ "type": "string"
+ },
+ "notes": {
+ "description": "Free-text bullet notes for the step.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Defaults to 'Available' when omitted. Unknown values are coerced server-side.",
+ "enum": [
+ "Hidden",
+ "Available",
+ "Active",
+ "Completed",
+ "Failed",
+ "TurnedIn",
+ "Abandoned",
+ "Expired",
+ "OnHold"
+ ],
+ "type": "string"
+ },
+ "stepId": {
+ "description": "Optional. Server generates a fresh UUID when blank. Provide an existing stepId to reuse linkedStepIds.",
+ "type": "string"
+ },
+ "targetLocationEntryIds": {
+ "description": "Locations involved in this step.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "targetNpcEntryIds": {
+ "description": "NPCs involved in this step (entryIds or titles).",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "title": {
+ "description": "Short label for the step, e.g. 'Talk to the innkeeper'.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "title"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with 'Create.' The description adds meaningful auth context (GM/co-GM only) not present in annotations, and there is no contradiction with the structured data.
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 two short sentences, front-loaded with the action ('Create Quest mnemons'). No filler or redundant detail—every word earns its place.
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?
The tool has a complex nested schema (items with steps, rewards, etc.) and two required parameters, but the description is sparse. It covers purpose and permission but omits any guidance on the items structure or campaign context. The rich schema and output schema compensate partially, yet the description feels incomplete for such a complex tool.
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?
The description mentions 'questStatus is one of active|completed|failed,' but this exactly duplicates the schema's existing description for that property, adding no new semantics. Top-level parameters campaignId and items are not explained in the description, and schema coverage is 0%, so the description fails to compensate.
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 clearly states the tool's function with a specific verb ('Create') and resource ('Quest mnemons'). This distinguishes it from sibling tools like create_npc_mnemons or create_lore_mnemons, making the purpose unambiguous.
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 provides an explicit permission boundary: 'Players may not call this — GM/co-GM only.' This is a clear usage exclusion, though it doesn't elaborate on when to prefer this over other create tools, which is largely self-evident from the resource type.
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.
Each tool has a clearly distinct purpose. The mnemon tools are separated by type (NPC, Location, Quest, etc.), and other domains like guild, forum, and friend management are also well-segmented. No two tools appear to do the same thing.
Most tools follow a consistent verb_noun pattern with snake_case. Some minor deviations: 'describe_mnemon_types' instead of 'list_mnemon_types', and 'invite_user_by_email' has a slightly different structure. Overall quite consistent.
With 63 tools, the server is quite heavy. While each tool serves a specific purpose for campaign management, the sheer number may be overwhelming. It is borderline but still reasonable given the broad domain coverage.
The tool set covers CRUD for most resources (campaigns, sessions, mnemon types, guilds, friends, forum). Notable gaps: no delete_campaign or delete_session, and update_campaign is limited. However, the core workflows are well-covered.