Skip to main content
Glama

Embers: Tabletop RPG Toolkit

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

imagine_unhide_world_stock
Idempotent

Stop hiding a stock record in a World, so its Characters are offered it again. Unhiding a record the World does not hide changes nothing. Returns { success: true }. 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_unhide_world_stock"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds the authorization requirement (owner, contributor, or admin in Admin Mode) and confirms the no-op case, which are genuine additions beyond the annotations; the return-value sentence largely duplicates the existing output schema.

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?

Three short sentences, front-loaded with the action and its effect, then edge case, then return value and permissions. The explicit return shape is mildly redundant given an output schema exists, but nothing is bloated.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with full schema coverage and an output schema, the description covers effect, idempotency edge case, authorization, and return shape. What remains unstated (e.g., whether existing character copies are affected) is minor for this scope of tool.

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%, and each parameter already carries a description including enum values and even discovery pointers (vault_search_rules/spells/items). The description adds no parameter-level meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource combination ('Stop hiding a stock record in a World') and even describes the observable effect ('its Characters are offered it again'), which makes the intent unambiguous. It does not name the inverse sibling (imagine_hide_world_stock) explicitly, so it stops short of full sibling differentiation.

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 supplies a useful precondition edge case ('Unhiding a record the World does not hide changes nothing') and a permission gate, which frames when the call is valid. It stops short of explicit guidance contrasting this with house-rule or other world-mutation siblings, so an agent must infer the boundary.

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