Skip to main content
Glama

server_list_files

List files and directories in a Minecraft server's directory to manage server content and structure.

Instructions

List files and directories in a Minecraft server's directory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
pathNoRelative path to list (empty string for root)

Implementation Reference

  • The tool 'server_list_files' is registered using server.tool, with the implementation directly defined in the handler function that calls the CraftyClient.
    server.tool(
      "server_list_files",
      "List files and directories in a Minecraft server's directory",
      {
        server_id: z.string().describe("Server ID or UUID"),
        path: z.string().default("").describe("Relative path to list (empty string for root)"),
      },
      async ({ server_id, path }) => {
        try {
          const data = await client.post(`/servers/${server_id}/files`, { path });
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a listing operation, implying read-only behavior, but doesn't disclose critical details like whether it requires authentication, returns paginated results, includes hidden files, handles errors, or has rate limits. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a straightforward listing tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (listing files/directories), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral context, usage guidelines, and output details, leaving the agent to infer or guess about the operation's full scope and behavior.

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 description coverage is 100%, so the schema already documents both parameters ('server_id' and 'path') thoroughly. The description adds no additional parameter semantics beyond what's in the schema, such as path format examples or server_id constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('List') and resource ('files and directories in a Minecraft server's directory'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'server_get_file' or 'server_list_backups', which would require a more precise scope definition.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'server_get_file' (for retrieving specific file content) and 'server_list_backups' (for listing backups), there's no indication of context, prerequisites, or exclusions for this directory listing operation.

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/HadiCherkaoui/crafty-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server