Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update-folder

Update an existing sidebar folder in place: rename, recolor, set sort order, or reparent to another folder or root. Resolves by exact id or name+type, skipping the move-documents and delete-folder workflow. GM-only.

Instructions

Update a sidebar Folder in place — rename it, recolor it, set its raw sort, and/or reparent it (nest under another folder of the same type, or pass parentFolder:"" to move it to the root). Resolves the folder by exact id or exact name+type. Use this to RENAME a folder without the move-documents + delete-folder dance. To reposition a folder, RENAME it — sort does not drive folder order in the v14 sidebar. GM-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew folder name (rename).
sortNoThe Folder document's sort value. ⚠️ ADVISORY, not a lever: writing it persists and reads back, but the v14 sidebar was observed rendering sibling FOLDERS ALPHABETICALLY BY NAME regardless of it (verified live 2026-08-12 on Scene folders — 100000/200000/300000 against siblings at 0 did not move them). To control folder ORDER, control the NAME (this world uses "NN - " prefixes, 99 for undetermined).
typeNoFolder document type (needed to resolve by name; default Actor).Actor
colorNoNew hex color, e.g. "#4a90e2".
identifierYesFolder id or exact name to update.
parentFolderNoReparent under this folder id or exact name (same type). "" = move to root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.3
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "The Folder document's sort value. ⚠️ ADVISORY, not a lever: writing it persists and reads back, but the v14 sidebar was observed rendering sibling FOLDERS ALPHABETICALLY BY NAME regardless of it (verified live 2026-08-12 on Scene folders — 100000/200000/300000 against siblings at 0 did not move them). To control folder ORDER, control the NAME (this world uses \"NN - \" prefixes, 99 for undetermined).",
+  "type": "integer"
+}
  2. Addedv1.3.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does well: it explains resolution by exact id or name+type, reveals that `sort` is advisory and verified not to reorder folders, and notes GM-only access. It could add what happens on failure (e.g., not-found behavior), but the coverage is strong.

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 dense but well-organized: it front-loads the primary purposeaine the operations, then adds resolution and usage caveats. The long `sort` warning is essential and earns its place because it prevents a plausible misuse. No filler or repetition.

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?

For a 6-parameter mutation tool with no output schema, the description covers every operation, all parameter semantics, resolution rules, permission scope, and a key behavioral caveat about sidebar ordering. An agent has enough information to invoke this tool correctly and avoid the main trap.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description adds substantial semantic context beyond the schema: `sort` is explicitly labeled as non-driving for folder order, `parentFolder: ""` means move to root, and `identifier` resolution semantics are clarified. This meaningfully helps an agent choose and fill parameters correctly.

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 names a specific verb ('Update'), a specific resource ('sidebar Folder'), and lists the concrete operations: rename, recolor, set sort, and reparent. It also explicitly differentiates this tool from siblings by stating 'Use this to RENAME a folder without the move-documents + delete-folder dance,' which makes its purpose unambiguous.

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?

The description gives clear when-to-use guidance: renaming a folder without the move-documents/delete-folder workaroundhol. It also warns against using `sort` to reposition folders because it does not drive v14 sidebar order, and states GM-only permission. These exclusions and alternatives are explicit.

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