Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apply-condition

Apply or remove D&D 5e conditions on an actor, including blinded, frightened, poisoned, and exhaustion. Set active=false to remove conditions, and use exhaustionLevel to set exhaustion from 1 to 6.

Instructions

[D&D 5e only] Apply or remove one or more conditions on an actor (blinded, frightened, grappled, poisoned, prone, restrained, stunned, unconscious, exhaustion, ...). Set active=false to remove. Exhaustion is leveled — pass exhaustionLevel (1-6; 0 removes). This authors condition state on a creature; it is NOT a combat-automation loop (no duration countdown / save-ends handling). Use list-actors or get-actor to find the actorIdentifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNotrue applies the conditions (default); false removes them.
conditionsYesCondition ids to toggle: blinded, charmed, deafened, frightened, grappled, incapacitated, invisible, paralyzed, petrified, poisoned, prone, restrained, stunned, unconscious, exhaustion, and the other dnd5e conditionTypes/statusEffects (coverHalf, coverThreeQuarters, coverTotal, concentrating, heavilyEncumbered, ...). Matched case-insensitively.
actorIdentifierYesName or id of the actor (partial name match supported). Also accepts a placed TOKEN id (from list-tokens) — the condition then applies to that token INSTANCE only, not the base actor.
exhaustionLevelNoExhaustion level 1-6 (0 removes it). Only affects the "exhaustion" condition, and only when applying — with active=false the condition is removed regardless of this value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.3
    • changedInput schema / properties / conditions / description
      Previous value: -"Condition ids to toggle: blinded, charmed, deafened, frightened, grappled, incapacitated, invisible, paralyzed, petrified, poisoned, prone, restrained, stunned, unconscious, exhaustion, and the other dnd5e conditionTypes/statusEffects."New value: +"Condition ids to toggle: blinded, charmed, deafened, frightened, grappled, incapacitated, invisible, paralyzed, petrified, poisoned, prone, restrained, stunned, unconscious, exhaustion, and the other dnd5e conditionTypes/statusEffects (coverHalf, coverThreeQuarters, coverTotal, concentrating, heavilyEncumbered, ...). Matched case-insensitively."
    • changedInput schema / properties / exhaustionLevel / description
      Previous value: -"Exhaustion level 1-6 (0 removes it). Only affects the \"exhaustion\" condition."New value: +"Exhaustion level 1-6 (0 removes it). Only affects the \"exhaustion\" condition, and only when applying — with active=false the condition is removed regardless of this value."
  2. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / actorIdentifier / description
      Previous value: -"Name or id of the actor (partial name match supported)."New value: +"Name or id of the actor (partial name match supported). Also accepts a placed TOKEN id (from list-tokens) — the condition then applies to that token INSTANCE only, not the base actor."
  3. First observedv1.2.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses D&D 5e-only scope, active=false toggling removal, leveled exhaustion, token-instance behavior, and that this authors state rather than automating combat. Missing permission/reversibility details, but strong overall.

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?

Compact and well-structured: purpose first, then key modifiers, then an explicit non-goal, then a lookup hint. Every sentence adds value without fluff.

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?

Covers operation, removal behavior, exhaustion special case, token-id nuance, and how to find the required identifier. No output schema exists, but for a state-mutating tool the return value is not essential for correct selection or invocation.

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%, so every parameter is already documented. The description reinforces active=false and exhaustionLevel semantics but does not add meaning beyond what the schema already provides.

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: 'Apply or remove one or more conditions on an actor,' with concrete condition examples. It also distinguishes itself by explicitly saying it is NOT a combat-automation loop, helping an agent separate it from related effect/combat tools.

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?

Gives explicit when-not guidance: no duration countdown or save-ends handling, and directs the user to list-actors or get-actor to find the actorIdentifier. It does not name a specific sibling tool for automation, but the exclusion is clear enough for selection.

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