Skip to main content
Glama

List files on webspace

webspace_list_files
Read-only

List a directory inside a webspace as its unprivileged site user, jailed to the home directory. Returns per entry name, isDirectory, isSymlink, size, mode and mtimeMs. Read a file with webspace_read_file. For a VPS use vps_list_files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "path": "<path>"
    },
    "name": "webspace_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
pathYesPath relative to the webspace's home directory, or absolute under /home/<user>/. The web root is public_html.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context beyond that: the listing runs as the unprivileged site user and is jailed to the home directory, which tells the agent what it can and cannot see. It also enumerates the returned fields, useful since there is no output schema.

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?

Three short sentences, front-loaded with the action and scope, followed by return fields and then routing hints. Every sentence carries distinct information with no repetition.

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?

For a two-parameter read-only listing tool with no output schema, the description covers scope, permission context, return shape, and alternatives. Nothing an agent needs in order to call it correctly is missing.

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%, so both parameters (id, path) are already documented, including the relative-vs-absolute path rule and the public_html web root. The description's 'jailed to the home directory' reinforces the path constraint but adds no new syntax or format detail, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('List a directory inside a webspace') plus the execution context (unprivileged site user, jailed to home directory). It also names the sibling it is not (vps_list_files), so an agent can distinguish it without opening another schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use webspace_read_file to read a file, and vps_list_files for a VPS. Both the adjacent action and the adjacent resource type are covered, leaving little to inference.

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.