Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

apply-condition

Apply or remove D&D 5e conditions (blinded, poisoned, exhaustion) on an actor by name or token ID. Supports exhaustion levels and removal via active=false.

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.
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.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool authors condition state, is not an automation loop, and is D&D 5e only. It could mention permission requirements or reversibility, but overall transparency is good.

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?

The description is concise with two sentences plus a brief note. It is front-loaded with the core purpose and then adds specifics in a logical order. Every sentence earns its place without redundancy.

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?

Given the tool's complexity (4 params, no annotations, no output schema), the description covers purpose, usage, parameters, and system specificity. It could mention return behavior or effects on existing conditions, but remains fairly complete.

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%, but the description adds value: lists example conditions, explains exhaustionLevel semantics, and notes that actorIdentifier can accept a token ID for instance-specific application. This goes beyond the schema definitions.

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 clearly states the tool applies or removes conditions on an actor, listing specific condition examples. It distinguishes itself from siblings by explicitly noting it is not a combat-automation loop, which sets it apart from potential automation 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?

The description provides clear guidance on how to use: system-specific (D&D 5e), toggling with active boolean, exhaustion level handling, and how to find the actor identifier. While it doesn't explicitly list alternatives for similar tasks, the context is sufficient for correct usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Txpple/fvtt-mcp-molten5e'

If you have feedback or need assistance with the MCP directory API, please join our Discord server