Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_chmod

Read-onlyIdempotent

Convert Linux file permissions between octal and symbolic notation and generate the matching chmod command. Includes breakdown of owner/group/others rights, special bits, and security notes.

Instructions

Chmod Permission and Command Generator. Convert Linux file permissions between octal (e.g. 755, 4755) and symbolic (e.g. u+x, g-w, a=r) notation and assemble the matching chmod command string. For each permission it derives the owner/group/others read-write-execute breakdown, decodes special bits (setuid 4 / setgid 2 / sticky 1) on 4-digit octal, parses who/operation/perms for symbolic input, surfaces security notes (world-writable, 777, 600), and returns the literal chmod [-R] <perms> <path> command. It only BUILDS the command text — it never runs chmod, changes any mode, or touches the filesystem. Use it to look up or teach permission values and produce a copy-paste command; use linux_command_builder for find/grep/rsync/tar commands, linux_user_group_manager for useradd/usermod, and octal/base converters for raw number-base math. Runs locally via a Node bridge: read-only, non-destructive, idempotent, offline, contacts no external service, and is rate-limited (anonymous 30/min, 200/hr, 1000/day).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
permissionsNoOne or more permission specs, each processed independently. Each is octal (3 or 4 digits, 0-7 per digit; a 4th leading digit is special bits) or symbolic ([ugoa][+-=][rwxXstugo]). Invalid entries return a per-result error.
pathNoTarget path interpolated verbatim into the command; not validated or accessed./path/to/file
recursiveNoWhen true, adds the -R flag (chmod -R) to recurse into directories.
symbolicNoHint that input is symbolic notation. Format is auto-detected regardless; this only influences UI/output framing.
explanationNoWhen true, includes the per-class breakdown and security_notes in each result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200 response.
resultsNoOne entry per input permission, in order.
Behavior4/5

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

The description discloses behavioral traits beyond annotations: 'It only BUILDS the command text — it never runs chmod, changes any mode, or touches the filesystem.' It also mentions idempotence, offline operation, and rate limits. Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context without contradiction.

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?

The description is well-structured with the most important information first. It is slightly verbose but each sentence adds value. The division into usage, behavior, and alternatives is clear. No wasted words, but could be trimmed slightly.

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?

Given the tool's complexity (5 parameters, diverse input formats) and the presence of an output schema, the description is complete. It covers purpose, usage, behavior, parameters, and safety. The agent can correctly select and invoke the tool.

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

Parameters5/5

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

The description adds meaningful detail beyond the input schema. For example, the permissions parameter explanation covers octal vs symbolic notation and special bits. The path parameter is described as 'interpolated verbatim'. The recursive, symbolic, and explanation parameters have clear semantics. Schema coverage is 100%, and the description enriches all parameters.

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 clearly states the tool's purpose: 'Chmod Permission and Command Generator. Convert Linux file permissions between octal and symbolic notation and assemble the matching chmod command string.' It distinguishes itself from siblings like linux_command_builder and linux_user_group_manager by explicitly naming alternatives.

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?

The description provides explicit guidance on when to use the tool: 'Use it to look up or teach permission values and produce a copy-paste command.' It also states when not to use it and suggests alternatives: 'use linux_command_builder for find/grep/rsync/tar commands, linux_user_group_manager for useradd/usermod, and octal/base converters for raw number-base math.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server