Skip to main content
Glama

List files in the server folder

list_files
Read-onlyIdempotent

Lists files and folders inside the Minecraft test server directory, such as world/datapacks, config or mods, at a chosen depth so you can inspect server contents.

Instructions

Lists files and folders inside the test server folder, for example world/datapacks, config or mods. Paths are relative to the server folder; nothing outside it can be listed.

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
pathNoFolder inside the server folder. Default the server folder itself..
depthNoHow many levels deep. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's one real addition is the sandbox boundary ('nothing outside it can be listed'), which usefully prevents traversal attempts. It says nothing about output format, ordering, or whether large trees are truncated.

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?

Two tight sentences: what it lists, examples, and the boundary constraint. The most important constraint is front-loaded and nothing is redundant with the title.

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?

This is a simple read-only, two-optional-parameter tool with rich annotations, and the description covers purpose and scope sufficiently. The only meaningful gap is return shape (flat list vs. nested recursive result, especially with depth>1), which is unspecified and there is no output schema.

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% and both parameters already document their defaults and bounds. The description adds the relative-path semantics ('Paths are relative to the server folder'), reinforcing the path parameter but not adding syntax or format information beyond the schema. Baseline 3 is appropriate.

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 and resource ('Lists files and folders') and scopes it to the server folder, with concrete examples (world/datapacks, config, mods) that make the target unambiguous. It doesn't explicitly contrast with read_file or other siblings, but the listing-vs-reading distinction is clear from the verb.

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

Usage Guidelines3/5

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

There is no explicit when-to-use guidance or named alternative (e.g., 'use read_file to view contents of a listed file'). Usage is only implied by the scope constraint that nothing outside the server folder can be listed. An agent can infer the browsing role, but the description never routes it.

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