Skip to main content
Glama

chmod_item

Changes file or directory permissions on a cPanel server using a 4-digit octal mode, such as 0644 for files or 0755 for directories.

Instructions

Change file or directory permissions (chmod) on the cPanel server (e.g., 0644 or 0755).

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": {
      "path": "<path>",
      "permissions": "<permissions>"
    },
    "name": "chmod_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRelative path of the file or folder.
permissionsYes4-digit octal permission mode (e.g., 0644 for files, 0755 for directories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/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 behavioral burden. It signals a mutation but says nothing about required privileges, whether the operation is recursive, what happens on a nonexistent path, or how failures are surfaced — significant gaps for a no-annotation mutation tool.

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 the verb and resource first, zero padding. The parenthetical examples are slightly redundant with the schema but do not bloat the definition.

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 simple two-parameter operation with full schema coverage and no output schema, the essentials are present. However, with no annotations at all, the description should have covered error behavior and permission prerequisites to be complete.

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 coverage is 100% and both parameters are fully documented in the schema, so the baseline is 3. The description's example modes (0644, 0755) duplicate what the schema already states rather than adding new meaning such as validation rules or path resolution behavior.

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 ('Change') and resource ('file or directory permissions') plus the chmod equivalent and target platform (cPanel server). The operation is unambiguous and clearly distinct from siblings like write_file or delete_item, though no sibling is named explicitly.

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?

The chmod framing implies when to use it (adjusting permissions), but there is no explicit when-to-use versus alternatives, no note that the target must already exist, and no mention of ownership or privilege prerequisites needed to successfully change permissions.

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