Skip to main content
Glama
Txpple

fvtt-mcp-molten5e

by Txpple

upload-asset-tree

Recursively upload a local directory of assets to Foundry VTT over WebDAV, maintaining folder structure and skipping duplicates. Supports extension filtering and overwrite option.

Instructions

Plane B (file channel, write). Recursively upload a LOCAL directory tree of ASSETS to the Foundry data area over WebDAV, preserving the subtree layout (each file → remoteRoot/), creating parent folders as needed. Use for BULK imports — a scene pack's images, a tiles folder — instead of one upload-asset per file. Skips files that already exist unless overwrite:true; optional includeExt filter (e.g. ["webp"]). ASSETS ONLY — refuses live world-DB paths. Reports uploaded/skipped/error counts. PRIVACY: anything under Data/ is served publicly with no auth. Requires MOLTEN_WEBDAV_PASSWORD.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localRootYesAbsolute path to a LOCAL directory; every file under it (recursive) is uploaded.
overwriteNoOverwrite existing files (otherwise an already-present file is skipped).
includeExtNoOnly upload files with these extensions (no dot, case-insensitive), e.g. ["webp","png","jpg"]. Omit to upload every file.
remoteRootYesDestination directory RELATIVE TO the Foundry `Data/` root, e.g. "worlds/your-world/assets/tom-cartos/<id>/tiles". Each local file lands at remoteRoot/<path-relative-to-localRoot>. Never inside a world's `data/` (LevelDB) dir.
Behavior4/5

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

With no annotations, the description discloses key behaviors: creating parent folders, skipping existing files unless overwrite, optional includeExt filter, reporting counts, and privacy implications. It does not mention rate limits or performance but covers essential traits.

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 description is somewhat lengthy but well-structured with bullet points. Every sentence provides important information. The opening label 'Plane B (file channel, write)' is jargon but still informative.

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 4 parameters, no output schema, and no annotations, the description is fairly complete. It covers privacy, required environment variable, behavior on existing files, and error reporting. Could explicitly mention the return format, but the report counts are implied.

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%, so baseline is 3. The description adds context beyond the schema: explains localRoot as absolute path, remoteRoot relative to Data/, the resulting file layout, and clarifies includeExt filtering. This adds value for correct usage.

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's purpose: recursively uploading a local directory tree of assets to Foundry data area, preserving subtree layout. It distinguishes from siblings (e.g., upload-asset) by emphasizing bulk imports and recursive upload.

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?

Provides explicit use cases (bulk imports, scene pack images, tiles folder) and a warning against world-DB paths. However, it lacks explicit when-not-to-use guidance and direct comparison to alternatives beyond 'instead of one upload-asset per file'.

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