Skip to main content
Glama

effect-toggle-status

Toggle a status condition on an actor, or on ONE token via tokenId (any game system; PF2e conditions with values use pf2e-set-condition / pf2e-remove-condition instead). Several copies of one actor: tokenId makes only that goblin prone.

Status IDs are the game system's. dnd5e: blinded, charmed, deafened, exhaustion, frightened, grappled, incapacitated, invisible, paralyzed, petrified, poisoned, prone, restrained, stunned, unconscious. swade: shaken, stunned, distracted, vulnerable, prone, …

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": {
      "statusId": "<statusId>"
    },
    "name": "effect-toggle-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeNotrue = add, false = remove; omitted = toggle
actorIdNoActor ID (from actor-list/actor-filter)
overlayNoShow as the large overlay icon
sceneIdNoScene of tokenId (default: active)
tokenIdNoToken ID (from token-list) instead of actorId: that token's own actor (module 8.14+)
statusIdYesStatus ID: "blinded", "poisoned", "prone", …

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / active / description
      Previous value: -"Explicitly set active state (true = add, false = remove). If not specified, toggles current state."New value: +"true = add, false = remove; omitted = toggle"
    • changedInput schema / properties / actorId / description
      Previous value: -"The actor ID to toggle status on"New value: +"Actor ID (from actor-list/actor-filter)"
    • changedInput schema / properties / overlay / description
      Previous value: -"If true, shows as large overlay icon on token"New value: +"Show as the large overlay icon"
    • addedInput schema / properties / sceneId
      Added value: +{
      +  "description": "Scene of tokenId (default: active)",
      +  "type": "string"
      +}
    • changedInput schema / properties / statusId / description
      Previous value: -"The status/condition ID (e.g., \"blinded\", \"poisoned\", \"prone\")"New value: +"Status ID: \"blinded\", \"poisoned\", \"prone\", …"
    • addedInput schema / properties / tokenId
      Added value: +{
      +  "description": "Token ID (from token-list) instead of actorId: that token's own actor (module 8.14+)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "actorId",
      -  "statusId"
      -]New value: +[
      +  "statusId"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, idempotent=false, destructive=false), so the description's added value is scope behavior: tokenId affects only that token's own actor rather than every copy, and status IDs are governed by the game system. It stops short of stating permission/ownership requirements or what happens with an unrecognized statusId.

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?

The core action, token/actor rule, and the sibling exclusion are front-loaded in the first two sentences. The trailing status-ID list is useful reference but is a long, partially elided enumeration ('…') that pushes length without being exhaustive.

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 non-idempotent mutation with no output schema, the definition covers target selection (actor vs token), system-dependent ID vocabulary, and the PF2e escape hatch. Missing only permission/ownership expectations and error behavior for invalid status IDs — both worth knowing before calling.

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%, so all six parameters are already documented, setting the baseline at 3. The description does add genuine meaning to statusId by enumerating concrete IDs per game system (dnd5e, swade), which the schema's ellipsis-style example does not — nudging toward 4, but actorId/tokenId/overlay/sceneId gain nothing beyond the schema.

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+resource ('Toggle a status condition') and immediately narrows scope to actor-level vs. a single token via tokenId. It names the sibling alternatives (pf2e-set-condition / pf2e-remove-condition) that handle the value-bearing PF2e case, so an agent can tell this tool apart without opening schemas.

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

Usage Guidelines5/5

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

Explicit routing: use tokenId for ONE token (with a concrete scenario — duplicate goblin actors), actorId otherwise, and defer to PF2e-specific tools when conditions carry values. The 'any game system' clause also sets the applicable domain. This is when-to-use and when-not-to-use in two sentences.

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