Skip to main content
Glama
Sign In
aapanel-mcp

aapanel-mcp

by devochkaskustikom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Preview a site deletion

site_delete_check
Read-onlyIdempotent

Check what a website deletion would remove, including domains, databases, FTP accounts, and root directory. Preview the impact before calling site_delete.

Instructions

What a site deletion would take with it: associated domains, databases, FTP accounts and root directory. Always call this before site_delete so the user can see the blast radius.

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": {
      "id": "<id>"
    },
    "name": "site_delete_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebsite id to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1-alpha.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing what the inspection surfaces (associated domains, databases, FTP accounts, root directory), which is the tool's actual payload since no output schema exists. It stops short of noting permission requirements or that a preview does not guarantee the deletion will succeed.

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?

Two compact sentences with zero filler; the purpose/output enumeration comes first and the mandatory ordering call-out second. The opening nominal fragment is slightly indirect but still front-loads the meaning efficiently.

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?

With a single required parameter, full schema coverage, and no output schema, the description carries the burden of explaining what is returned and does so by listing the blast-radius components. Adding the pre-condition that the id must reference an existing site would make it fully 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?

Only one parameter exists at 100% schema coverage, and the schema already documents it as 'Website id to inspect.' The description does not add format, constraints, or lookup guidance beyond this, so the baseline of 3 applies.

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+resource (preview what a site deletion would remove) and enumerates the affected resources: domains, databases, FTP accounts, root directory. It is clearly distinguished from the sibling site_delete, which performs the actual removal.

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?

Explicitly states the condition and ordering: 'Always call this before site_delete so the user can see the blast radius.' The alternative (site_delete) is named and the relationship between the two is unambiguous.

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