Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Remove a rule, spell, or item from a World's house rules

imagine_remove_world_house_rule
DestructiveIdempotent

Take a rule, spell, or item off a World's house rules, and off the linked campaigns that have it from the World. Characters that already hold it keep it. The app answers 400 when the record is not one of the World's own house rules (one a linked campaign adds is removed on that campaign). Caller must be able to edit the World (its owner, a contributor, or an admin with Admin Mode on). Destructive. Confirm with the user first.

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>",
      "entityType": "<entityType>",
      "entityId": "<entityId>"
    },
    "name": "imagine_remove_world_house_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.
entityIdYesMongo `_id` of the vault rule, spell, or item. Find it with vault_search_rules, vault_search_spells, or vault_search_items.
entityTypeYesWhat kind of vault record `entityId` is.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds real information beyond them: cascading removal from linked campaigns, the fact that characters already holding the item keep it, the 400 error when the record is not the World's own house rule, and the permission requirement. It also explicitly labels the operation destructive and asks for user confirmation.

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 sentences plus two short directive fragments, with the action and cascade stated first and the caveats after. 'Destructive. Confirm with the user first.' is front-loaded at the end where the agent will act on it, and no sentence is filler.

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?

For a destructive mutation with 3 required parameters and an output schema, the description covers authorization, cascade side effects, error conditions, and post-state ('Characters that already hold it keep it'). Nothing an agent needs to invoke it safely is missing.

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% and each parameter is already documented, including the lookup pointers for entityId. The description echoes the rule/spell/item scope but adds no syntax, format, or edge-case meaning beyond what the schema supplies, so the baseline 3 applies.

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 object ('Take a rule, spell, or item off a World's house rules') plus the cascade scope ('off the linked campaigns that have it from the World'), which separates it from the campaign-level removal siblings such as play_remove_campaign_rule and from imagine_remove_world_skill. An agent can pick this tool without opening a 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?

Gives the caller a clear usage condition ('Caller must be able to edit the World (its owner, a contributor, or an admin with Admin Mode on)') and one exclusion ('one a linked campaign adds is removed on that campaign'), plus a 'Confirm with the user first' instruction. It stops short of naming the campaign-removal tool directly, so routing to the alternative is inferred rather than explicit.

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