Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Unlink a play campaign from a world

imagine_unlink_world_from_campaign
Idempotent

Unlink a play campaign from a world: removes the campaign from the world's playCampaignIds[]. Pass removeSyncedHouseRules: true to also remove the house rules the link shared between the world and the campaign. Unlinking takes no Character out of the World. The caller must be the campaign's owner or gamemaster. Caller must have 'edit' access on the world.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "campaignId": "<campaignId>"
    },
    "name": "imagine_unlink_world_from_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the world.
campaignIdYesMongo `_id` of the play campaign to unlink.
removeSyncedHouseRulesNoWhen true, also removes the house rules the link shared between the world and the campaign. Default false.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / removeSyncedHouseRules / description
      Previous value: -"When true, additionally cleans up any house rules that were synced into the world when the campaign was originally linked. Default false."New value: +"When true, also removes the house rules the link shared between the world and the campaign. Default false."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With annotations covering safety/idempotency, the description still adds substantial behavior: the exact collection field mutated, the optional cascading house-rule removal, the explicit non-effect on characters, and two concrete authorization requirements. This is more than the annotations convey and materially affects how an agent prepares the call.

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?

Front-loaded with the core action and effect, then permissions, with no filler sentences. The sentence describing `removeSyncedHouseRules` largely restates the schema's own parameter text, which is minor redundancy but not waste.

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

Completeness5/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 explained; the description instead covers mutation scope, opt-in cascading deletion, non-effects, and authorization. Nothing an agent needs to invoke this correctly appears to be missing.

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 already 100%, so the baseline is 3, but the description reinforces the meaning of `removeSyncedHouseRules` as an opt-in cascade rather than a default. It adds little on `id` and `campaignId` beyond the schema's own Mongo `_id` notes, so it is slightly above baseline rather than transformative.

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 and resource ('Unlink a play campaign from a world') and goes further to name the concrete data effect: removing the campaign from the world's `playCampaignIds[]`. This is clearly distinct from its inverse sibling `imagine_link_world_to_campaign` and from character-level tools like `imagine_remove_character_from_world`.

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?

Gives the precondition for use (caller must be campaign owner/gamemaster and have 'edit' access on the world) and an explicit exclusion ('Unlinking takes no Character out of the World'), which steers agents away from assuming character removal. It does not name a sibling to use instead for character or adventure unlinking, so it falls just short of full alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources