Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by aandersen2323
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cpanel_write_file

Write content to a file, creating or overwriting it. Specify the full file path and the content to write.

Instructions

Write content to a file (creates or overwrites)

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": {
      "file": "<file>",
      "content": "<content>"
    },
    "name": "cpanel_write_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesFull path to the file
contentYesContent to write to the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states 'creates or overwrites' which implies the core behavior, but lacks details on permissions, size limits, encoding, error handling, or side effects. Adequate but not thorough.

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?

One short sentence with no filler. Every word earns its place. It is front-loaded and to the point.

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 write tool with full schema coverage and no output schema, the description is adequate but incomplete: it doesn't specify overwrite behavior (truncation vs appending), file permissions, or supported content types. Sibling differentiation is missing.

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% with clear descriptions for both parameters (file path and content). The description adds no extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states the tool writes content to a file, with the parenthetical 'creates or overwrites' specifying the behavior. It uses a specific verb and resource, and implicitly distinguishes from siblings like cpanel_read_file and cpanel_delete_file.

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?

Description provides no guidance on when to use this tool versus alternatives (e.g., cpanel_read_file, cpanel_delete_file). There is no mention of prerequisites, context, or when not to use it.

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

Deploy Server

Other Tools