Skip to main content
Glama

file-list

Read-onlyIdempotent

List the directories and files of a folder in the Foundry data (read-only) — to find image, map and audio paths for scene-set, placeable-set and playlist-set. Paths are relative to the data root, e.g. "worlds/my-world/maps". Requires bridge module 8.19.0+.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "file-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoFolder path; default the root
bucketNos3 only
sourceNoDefault data (the user's files); public = Foundry's own icons and sounds
extensionsNoOnly these file types, e.g. ["webp","png"] or ["ogg","mp3"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the bridge module requirement (8.19.0+), the fact that paths are relative to a data root, and the data/public/s3 source distinction. It does not say whether listing is recursive or paginated, which is the remaining behavioral gap.

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 and scope are front-loaded in the first clause, followed by purpose and prerequisites. It is compact for the amount of information conveyed, though the em-dash clause packing three sibling tool names is dense and could be split.

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 4-parameter, all-optional, read-only listing tool with rich annotations and no output schema, the description covers purpose, path semantics, source meaning and a version prerequisite. The notable omission is return-shape detail — whether results are flat or recursive and whether they are paginated — which the agent cannot infer since no output schema exists.

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 the baseline is 3. The description adds genuine meaning on top by giving a concrete path format example ("worlds/my-world/maps") and clarifying root-relative semantics, which the schema alone does not convey. It adds nothing for bucket, source or extensions beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource ("List the directories and files of a folder") scoped to Foundry data and flags it as read-only. It further anchors the tool to a concrete workflow (finding image/map/audio paths for scene-set, placeable-set, playlist-set), which makes its role legible. It does not explicitly separate itself from the similarly named folder-list sibling, so a 4 rather than a 5.

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?

It states the concrete situation in which to reach for this tool (locating asset paths to feed into scene-set, placeable-set and playlist-set) and discloses the bridge version prerequisite. What is missing is explicit exclusion guidance — e.g. when to prefer folder-list for Foundry document folders instead of raw asset directories.

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