Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Hide a stock rule, spell, or item in a World

imagine_hide_world_stock
Idempotent

Hide a stock vault rule, spell, or item in a World: a Character in the World is no longer offered it in vault's pickers, character creation, or level-up, unless another World the Character is in does not hide it. Nothing is taken off any sheet; a Character that holds the record keeps it, and adding it by id still works. Hiding a record the World had added as a house rule takes it off the World's house rules and its linked campaigns. Stock records only (400 otherwise). Hiding a record already hidden changes nothing. Returns { hidden: { entityType, entityId, ruleset }, warning }; warning is set when the record could not be taken off every linked campaign. Only the World's owner, a contributor, or an admin with Admin Mode on may do this.

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_hide_world_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.
entityIdYesMongo `_id` of the STOCK vault rule, spell, or item (one the vault search tools return with `stock: true`). The app refuses any other record (400).
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?

Annotations already declare this a non-read-only, non-destructive, idempotent, open-world mutation, yet the description adds substantial behavior beyond them: nothing is removed from existing sheets, adding by id still works, cross-World interactions, campaign propagation with a warning case, idempotency semantics, a 400 for non-stock records, and the exact permission set (owner, contributor, admin with Admin Mode). This is a genuinely rich behavioral disclosure.

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?

Dense but front-loaded: the primary effect comes first, then edge cases, error behavior, and permissions. The only redundancy is restating the return shape `{ hidden, warning }` which the tool already exposes via an output schema.

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 an output schema (so return values need no further explanation), the description covers the side effects, cross-World precedence, house-rule interaction, idempotency, error condition, warning semantics, 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already documents `id` as the World's Mongo `_id`, `entityId` as a stock vault record `_id`, and `entityType` with its enum. The description reinforces the stock-only constraint and the `stock: true` provenance, but adds no new syntax or semantics for the parameters beyond the schema, 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?

The description opens with a specific verb and resource ("Hide a stock vault rule, spell, or item in a World") and immediately scopes it to stock records versus house-rule removal, which distinguishes it from siblings like imagine_remove_world_house_rule. An agent can tell what this mutates without opening the 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?

It clearly states the effect-based condition for use (the record is no longer offered in pickers, creation, or level-up) and notes the no-op case ("Hiding a record already hidden changes nothing"), so the agent can judge when the call is meaningful. It never explicitly routes to imagine_unhide_world_stock or names an alternative tool, so it stops short of a full when-to-use/when-not selection guide.

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