Skip to main content
Glama

Change permissions on VPS

vps_chmod
Destructive

Change file permissions on a VPS via SSH. Mode is an octal string (e.g. '0755') or decimal int 0-4095.

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>",
      "mode": "<mode>"
    },
    "name": "vps_chmod"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
modeYesOctal string '0755' or decimal int
pathYesAbsolute path

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is carried structurally. The description adds the transport detail ('via SSH') and the mode encoding, but does not say that existing permissions are overwritten, whether recursion into directories happens, or what happens on a nonexistent path — meaningful gaps for an operation flagged destructive.

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 sentences, zero filler, with the action and its channel front-loaded and the awkward parameter format flagged immediately after. Nothing is repeated and nothing needs trimming.

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?

For a three-required-parameter mutation with no output schema, the definition covers target, mode format and transport, and annotations cover the destructive profile. It is adequate but thin: error behavior, overwrite semantics, and the VPS-vs-webspace decision are all left unaddressed.

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 the schema already documents all three parameters including the '0755' or decimal int mode. The description largely restates the mode constraint and adds the 0-4095 range context, which is close to duplicating structured data rather than extending it; path semantics (absolute, must exist, symlinks) are untouched.

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 and resource ('Change file permissions') plus the execution channel ('on a VPS via SSH'), which lets an agent distinguish it from unrelated siblings like vps_power or vps_mkdir. It stops short of naming the obvious near-neighbor webspace_chmod, so the VPS-vs-webspace split must be inferred from the title rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance and no pointer to an alternative tool for the webspace case. The only implicit signal is 'via SSH', which tells the agent the target must be SSH-reachable but not when this tool should be preferred over vps_exec running a chmod command.

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.