Skip to main content
Glama

list_files

List all files and directories in a cPanel directory, including dotfiles, permissions, and sizes, to inspect contents and audit file details.

Instructions

List all files and directories (including dotfiles, permissions, and sizes) inside a cPanel directory.

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
dirNoRelative path inside ALLOWED_ROOT (leave empty for root).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does add value by disclosing what the listing includes (dotfiles, permissions, sizes). However, it does not state whether listing is recursive, whether output is paginated or size-limited, or what permission constraints apply.

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?

A single sentence that is front-loaded with the verb and resource and wastes no words, while still packing in useful detail about the returned fields.

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 one-parameter read-only listing tool with no annotations and no output schema, the description covers purpose, scope, and the shape of returned entries adequately. Missing depth on recursion or limits is a minor gap given the tool's simplicity.

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% for the single `dir` parameter, so the schema already documents the relative-path and empty-for-root semantics. The description adds only the framing that the directory is inside a cPanel root, which is marginal beyond the schema.

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 states a specific verb ("List") and resource ("files and directories") with a clear scope ("inside a cPanel directory"). This distinguishes it from mutating siblings like delete_item or read_file, though it does not explicitly name a sibling.

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?

Usage is implied by "List" — an agent can infer this is the browse/enumerate operation — but there is no explicit statement of when to prefer it over read_file or how to handle subdirectories. No exclusions or prerequisites are given.

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