Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create-rolltable

Build a random encounter, loot, or treasure table from text results and premium item UUID links. Auto-assigns roll ranges from weights, using a default 1d total weight formula.

Instructions

Create a RollTable from a list of results. Each result is literal text and/or a uuid referencing a REAL premium-book item (rendered as a clickable @UUID link — the way the published loot tables are built; SRD refs are refused). Ranges are auto-assigned from weights (and the formula defaults to 1d) unless you provide explicit ranges/formula. Use for random encounter/loot/rumour/treasure tables. GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTable name.
formulaNoRoll formula (default 1d<total weight>), e.g. "1d20".
resultsYesTable entries.
folderNameNoOptional folder to place the table in (created if absent).
descriptionNoOptional table description.
displayRollNoShow the roll when drawing (default true).
replacementNoDraw with replacement (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.3
    • addedInput schema / properties / results / items / properties / range / items
      Added value: +false
    • addedInput schema / properties / results / items / properties / range / maxItems
      Added value: +2
    • addedInput schema / properties / results / items / properties / range / minItems
      Added value: +2
  2. First observedv1.2.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers: it discloses premium-book-only refs, that SRD refs are refused, that ranges are auto-assigned from weights, that the formula defaults to 1d<total weight>, and that results render as clickable @UUID links. Failure/error behavior and the return contract are not covered, but the disclosed behaviors go well beyond a typical create stub.

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 information-dense sentences with the core action front-loaded. The premium/SRD restriction, auto-assignment behavior, defaults, and use case each earn their place; no words are wasted.

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 7-parameter create tool with no annotations and no output schema, the description plus a 100%-covered schema give an agent everything needed to construct valid results (text/uuid rules, weights, ranges, GM-only authorization). The only real gap is the return value, which is not described in either the description or the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

Schema coverage is 100% and the schema already documents the formula default and range auto-assignment, so the baseline is 3. The description adds cross-parameter semantics — how literal text and/or uuid combine per result and how weights drive range mapping — which adds value beyond the individual parameter descriptions.

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?

Leads with a specific verb+resource ('Create a RollTable from a list of results'), names the input form (a list of results) and the target use (random encounter/loot/rumour/treasure tables). This distinguishes it from siblings like create-cards, import-rolltable, and update-rolltable.

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?

'Use for random encounter/loot/rumour/treasure tables' is explicit when-to-use direction, and the GM-only constraint adds a clear authorization guard. It doesn't name alternatives or negative cases (e.g., when to prefer import-rolltable over this), so it stops one step short of full routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools