Skip to main content
Glama

Embers: Tabletop RPG Toolkit

List a World's house rules, hidden stock, extra skills, and extra damage types

imagine_list_world_house_rules
Read-onlyIdempotent

Read a World's house ruleset in one call. Returns houseRuleAssociations ({ world, campaigns, combined }: the rules, spells, and items the World adds as house rules, those its linked campaigns add, and the two merged, each row naming its entityType, entityId, and the contexts that add it), hidden (the stock records the World hides, [{ _id, name, type, ruleset, entityType }]), and houseSkills (the World's extra skills, [{ _id, ruleset, name, attribute, description }]), and houseDamageTypes (the World's extra damage types, [{ _id, ruleset, name }]). A Character in the World is offered stock content plus what its Worlds add, less the stock every one of its Worlds hides, gets the extra skills of its ruleset, and is offered the extra damage types of its ruleset in its sheet's damage line and damage type list editors. Only the World's owner, a contributor, or an admin with Admin Mode on may read this (403 otherwise).

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>"
    },
    "name": "imagine_list_world_house_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMongo `_id` of the World.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the permission gate ('owner, a contributor, or an admin with Admin Mode on may read this (403 otherwise)'). Its long enumeration of returned structures largely restates what the existing output schema already carries, which caps it at a 3 rather than higher.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a tight, front-loaded statement of purpose, which is good. The remainder is one enormous run-on sentence packing four nested return structures into a single clause chain, which makes it hard to scan even though the content is relevant.

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 exhaustively restating return fields is not strictly required, yet the description goes further by explaining the downstream meaning of the data (how a Character's available stock, skills, and damage types are computed). Combined with the explicit authorization rule, an agent has everything needed to decide whether and how to call it.

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% on the single `id` parameter, so the schema already documents it as a Mongo `_id`. The description adds no syntax, format, or lookup guidance for the id, leaving the schema to do all the work — the expected baseline of 3.

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 opening sentence names a specific verb and resource ('Read a World's house ruleset') and the title enumerates exactly the four payloads returned. An agent can distinguish this from the sibling mutation tools (add/remove house rule, hide/unhide stock) without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'in one call' hints that this is the aggregate read for World ruleset data, implying usage over piecemeal reads. However, no alternative is named and no when-not condition is stated, so the routing signal is implied 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