Skip to main content
Glama

Write file on VPS

vps_write_file
Destructive

Write content to a file on a VPS via SFTP. Parent directories are created automatically. Refuses critical system paths. Max 32 MB.

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>",
      "content": "<content>"
    },
    "name": "vps_write_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
pathYesAbsolute path of the file to write
contentYesThe file content to write
encodingNoContent encoding (default utf8). Use base64 for binary files.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutation and its destructive nature, and the description adds genuinely non-obvious behavior: automatic parent-directory creation, a refusal guard on critical system paths, and a 32 MB size cap. The notable gap is overwrite semantics — whether an existing file at the path is replaced or the call fails is not stated, which matters for a destructiveHint=true tool.

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?

Four short, front-loaded sentences: operation first, then automatic directory creation, then the safety guard, then the size limit. Nothing is repeated from the schema or annotations and no sentence is filler.

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 four-parameter mutation tool with annotations covering the safety profile and no output schema, the description supplies the operational constraints an agent needs (size limit, path guard, directory creation). Only the overwrite/return behavior is left unstated, a modest gap given the annotation coverage.

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 path, content, id and the utf8/base64 encoding enum are already fully documented in the schema including the binary-file hint. The description adds no parameter-level detail beyond what the schema provides, 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?

Specific verb+resource ("Write content to a file on a VPS") plus the transport (SFTP), so an agent knows exactly what operation this performs. It does not explicitly contrast with the close sibling webspace_write_file or vps_read_file, so differentiation is left to the name.

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?

Implicit usage is clear from the verb, and the "refuses critical system paths" note signals an exclusion zone. However, there is no explicit guidance on when to prefer this over webspace_write_file, or when to use vps_mkdir versus relying on automatic parent-directory creation.

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.