Skip to main content
Glama

Folder

list_files
Read-onlyIdempotent

Browse Minecraft server folders to see file names, sizes, modification times, and read/edit access; optionally list server and plugin config files.

Instructions

A folder of the server: names, folders first, sizes, modification times, and whether read_file and edit_file (with files:write) accept each. Paths are relative to the server folder, with forward slashes, such as server.properties, config/paper-global.yml, or plugins/TAB/config.yml. Files under logs/ need logs:read; the rest need files:read. WorldAPI's own folder, hidden files, keys, databases, and jars are never shared. logs lists the console logs: latest.log and older ones like 2026-10-19-1.log.gz. configs true answers instead where the server's own configs are (server.properties, bukkit.yml, spigot.yml, Paper's, and more) and each plugin's config files (needs files:read).

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": "list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoThe folder; the server folder itself when left out
configsNoList the server's and plugins' config files instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only annotations, the description adds substantial behavioral context: ordering, returned metadata, path format, required permissions, excluded items, special handling of logs, and the alternate configs mode. This gives an agent a strong picture of what the tool will and will not expose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense but structured as a long run-on sequence with semicolons and lacks a clear front-loaded verb. Most details are relevant, but the presentation could be much easier to scan.

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?

There is no output schema, so the description carries the burden of explaining return contents, and it does so thoroughly: names, ordering, sizes, modification times, read/edit compatibility, permissions, exclusions, and special modes. An agent has enough context to call this correctly.

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, but the description adds useful meaning: omitted path defaults to the server folder, path syntax uses forward slashes, and `configs true` changes the listing target to server and plugin config files. These details go beyond the schema's brief parameter descriptions.

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 conveys that the tool lists folder contents and details returned metadata, paths, and special modes. It distinguishes itself from read_file/edit_file by noting whether those tools accept each listed item, though it does not explicitly name list_plugins as an alternative for plugin listings.

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 path conventions, permission requirements for logs/ versus other files, and an explicit alternative mode via `configs true` for server and plugin config files. It does not comprehensively compare against every sibling listing tool, but the key routing conditions are clear.

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