Skip to main content
Glama

List files on VPS

vps_list_files
Read-only

List directory contents on a VPS via SFTP. Returns file names, types, sizes, modes, and modification times.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
pathYesAbsolute path of the directory to list

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true in annotations already establishes the safety profile, so the bar is lower. The description earns some credit for enumerating the returned fields, but omits what happens on a nonexistent or permission-denied path, whether hidden entries are included, and whether results are truncated for large directories.

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 short sentences, front-loaded with the action and transport, followed by the return contents. No filler or redundant restatement of 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?

No output schema exists, so the description usefully names the return fields; with only two fully documented parameters the definition is close to complete. Minor gap: nothing about empty directories, large listings, or error responses, though these are modest concerns for a read-only listing tool.

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% and both parameters are documented there (VPS ID with a 24-hex pattern, absolute directory path). The description adds no syntax, formatting, or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('List directory contents on a VPS') and names the transport (SFTP), which separates it from vps_read_file and the instance-level vps_list. It stops short of explicitly distinguishing itself from siblings like webspace_list_files, so it lands at clear-but-undifferentiated.

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 the resource name — an agent can infer 'use this to enumerate a remote directory'. But there is no statement of when to prefer vps_read_file for a single file, no note that path must be a directory rather than a file, and no mention of alternatives.

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.