Skip to main content
Glama
devochkaskustikom

aapanel-mcp

by devochkaskustikom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a website

site_create

Create a PHP website with optional FTP and MySQL accounts in one API call, returning generated credentials once so they can be captured before they are lost.

Instructions

Create a PHP site, optionally with an FTP account and a MySQL database in one call. The panel generates passwords; the response returns them once, so capture them for the user rather than logging them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
psNoHuman-readable remark shown in the panel.
ftpNoAlso create an FTP account.
sqlNoAlso create a MySQL database.
pathYesAbsolute root directory, e.g. /www/wwwroot/example.com.
portNoWeb port.
typeNoProject type; "PHP" for a PHP site.PHP
codeingNoDatabase charset when sql is true.utf8mb4
set_sslNo0 = no certificate, 1 = request one.
type_idNoGroup id from site_types; 0 is default.
versionYesPHP version from site_php_versions, e.g. "82" or "00" for static.
webnameYesJSON: {"domain":"example.com","domainlist":[],"count":0}
datauserNoDatabase name/user; required when sql is true.
force_sslNo0 = keep HTTP, 1 = force HTTPS redirect.
datapasswordNoDatabase password; required when sql is true.
ftp_passwordNoFTP password; required when ftp is true.
ftp_usernameNoFTP username; required when ftp is true.
is_create_default_fileNoCreate the default index page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1-alpha.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare it a non-readOnly, non-destructive, non-idempotent, open-world write. The description adds genuinely new behavioral context: the panel auto-generates passwords, and they are returned exactly once, so the agent must capture and not log them. That is high-value operational detail the annotations cannot convey.

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?

Two sentences, no filler, and the core action plus the optional composite scope are front-loaded before the credential warning. Every clause earns its place.

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

Completeness4/5

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

For a 17-parameter, no-output-schema mutation tool, the description covers the action, the optional sub-resources, and the critical credential-return behavior. It could say more about what the response contains or that creation requires subsequent site_delete to undo, keeping it from a 5.

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 description coverage is 100%, so baseline is 3; the description nonetheless adds meaning by clarifying that FTP/DB credentials are panel-generated rather than supplied, which reframes parameters the schema marks as 'required when ftp/sql is true'. It stops short of explaining the remaining 15 parameters' interplay, so it is not 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?

States a specific verb and resource ('Create a PHP site') plus the composite scope (optional FTP account and MySQL database in one call). This clearly separates it from siblings like db_create, site_delete, or site_add_domain.

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 phrase 'optionally with an FTP account and a MySQL database in one call' implies the user can consolidate provisioning here rather than chaining db_create and FTP calls, but there is no explicit when-to-use/when-not guidance or named alternative. Usage is implied, not stated.

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