Skip to main content
Glama

chmod

Set or update a file's permissions on a remote host by providing the host, path, and octal mode, enabling access control changes through Detour.

Instructions

Change a file's permissions on a host.

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": {
      "host": "<host>",
      "path": "<path>",
      "mode": "<mode>"
    },
    "name": "chmod"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
modeYesOctal permissions, like "755" or "644".
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and largely fails: it does not say whether the mode replaces or augments existing permissions, whether directories/recursion are supported, what permissions or session the caller needs, or what failures look like. Only the implied mutation and remote-host targeting are conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words; the operation and target are stated immediately. Brevity is not the problem here — the sentence simply stops before conveying the details an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation tool with no annotations, no output schema, and only one-third schema coverage, the definition is too thin. It omits permission prerequisites, session/host addressing, and result semantics that an agent needs to invoke it safely.

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

Parameters2/5

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

Schema coverage is 33% — only mode is documented ("Octal permissions, like \"755\" or \"644\""). The description adds no meaning for host (hostname, alias, or ID?) or path (absolute vs relative?), so the low coverage is not compensated.

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?

The description gives a specific verb and resource ("Change a file's permissions") plus the target scope ("on a host"), which is unambiguous about what operation is performed. It does not differentiate from siblings such as run_command, which could equally change permissions, so it falls short of a 5.

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 guidance on when to use this tool versus running a chmod through run_command or a snippet, and no stated prerequisites such as the need for an open session or elevated privileges. The agent must infer the context entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.