aapanel-mcp

Anti-cross-site settings

site_dir_userini

Read-onlyIdempotent

Get a site's .user.ini anti-cross-site protection and access-log flags plus its current run directory via site ID and root path.

Instructions

The .user.ini anti-cross-site protection flag, access-log flag and the current run directory of a site.

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>",
      "path": "<path>"
    },
    "name": "site_dir_userini"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Website id.
`path`	Yes	Website root path, from site_get_root.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1-alpha.0Sep 29, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description contributes the list of values read (anti-cross-site flag, access-log flag, run directory), which is real content-level information not present in annotations or schema, but it adds nothing about permissions or result format.

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 compact sentence with no filler, though it is phrased as a noun fragment rather than a complete statement of action, which slightly weakens front-loading.

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?

With no output schema, enumerating the returned flags is genuinely useful and partially compensates. However, it remains unclear what format the flags take or how the run directory is returned, leaving the description only adequately complete for a two-parameter read tool.

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 description coverage is 100% for both required parameters (id, path), so the schema documents them adequately. The description adds no parameter-level meaning, which is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (.user.ini flags plus the site run directory) but never states a verb, so the agent must infer that this is the read counterpart of site_set_dir_userini. The sibling setter makes the read/edit split inferable from the name pairing, but the description itself does no differentiating work.

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?

There is no when-to-use guidance, no prerequisite mention (e.g., needing a path from site_get_root, which the schema does cover), and no explicit routing away from site_set_dir_userini. Usage is only implied by the tool name.

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

Deploy Server