Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Add a rule, spell, or item to a World's house rules

imagine_add_world_house_rule
Idempotent

Add a vault rule, spell, or item to a World's house rules. Every Character in the World whose ruleset matches the record's is offered it (in vault's pickers, character creation, and level-up), and the World's linked campaigns get it as a house rule too. Adding a stock record the World hides makes it a house rule instead. Adding a record the World already has changes nothing. Caller must be able to edit the World (its owner, a contributor, or an admin with Admin Mode on).

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_add_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.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing propagation effects: every matching Character gets the record in pickers, character creation, and level-up, and linked campaigns receive it as a house rule. It also gives concrete semantics for idempotentHint ('already has changes nothing') and spells out the auth requirement (owner, contributor, or admin with Admin Mode on).

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 action, followed by consequence, edge cases, and permissions, and every sentence carries information. The propagation sentence is long and packs several distinct behaviors into one clause chain, which slightly hurts scanability.

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 3-parameter mutation with full schema coverage, rich annotations, and an output schema, the description supplies the remaining essentials: side effects on characters and campaigns, idempotency behavior, and authorization requirements. Nothing an agent needs before calling it 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 coverage is 100%, so id, entityId, and entityType are already documented, including how to find entityId via the vault search tools. The description mirrors but does not extend that meaning, 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 resource: 'Add a vault rule, spell, or item to a World's house rules.' The three entity kinds match the entityType enum, and the phrasing distinguishes it from the list/remove siblings without ambiguity.

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 conditions that change the outcome: records the World hides become house rules, and records it already has are a no-op. It also states the editing permission required. It does not explicitly say when to prefer this over a campaign-level add (e.g. play_add_campaign_rule), leaving that comparison to inference.

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