Skip to main content
Glama

Change permissions on webspace

webspace_chmod
Destructive

Change the permission bits of one file or directory inside a webspace (not recursive), as its site user, jailed to the home directory. Usual modes: 0644 for files, 0755 for directories, 0600 for files with secrets such as database passwords. A wrong mode can take the site offline or expose a secret. For a VPS use vps_chmod.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
modeYesOctal string such as '0644', or the same value as a decimal number (420)
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.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds context annotations cannot carry: execution happens as the site user, the operation is jailed to the home directory, it is not recursive, and a wrong mode can take the site offline or expose a secret. The stated blast radius is exactly the failure information an agent needs before invoking a destructive write.

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 sentences, all load-bearing: scope and jail first, practical mode guidance second, risk statement and the VPS alternative last. There is no filler or repetition of what the schema or annotations already state.

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?

With three fully documented parameters, no output schema, and destructive annotations already in place, the description supplies the remaining essentials: non-recursive behavior, execution identity, jail boundary, and consequence of error. Nothing an agent needs to call this safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description then adds genuine meaning by recommending specific mode values per use case (0644, 0755, 0600 for secrets), which the schema's generic octal/decimal note does not convey. Path and id semantics are left entirely to the schema, so it stops short of a 5.

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?

The description names a specific verb and resource ('Change the permission bits of one file or directory inside a webspace') and immediately bounds scope with '(not recursive)' and 'as its site user, jailed to the home directory'. It also names the sibling it is not ('For a VPS use vps_chmod'), so an agent can distinguish it from vps_chmod without opening either 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?

It gives an explicit selection rule against the closest alternative ('For a VPS use vps_chmod') and states the non-recursive constraint that determines when this tool is the wrong choice for directory trees. It further guides usage with concrete recommended modes (0644 files, 0755 directories, 0600 secrets), so the agent knows both when to call it and how to pick arguments.

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.