Skip to main content
Glama
Sign In
aapanel-mcp

aapanel-mcp

by devochkaskustikom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Toggle anti-cross-site protection

site_set_dir_userini

Toggle the .user.ini cross-site protection for a website by providing its ID and root path. Use this to enable or disable PHP open_basedir security restrictions.

Instructions

Toggle the .user.ini cross-site protection for 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_set_dir_userini"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWebsite id.
pathYesWebsite root path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1-alpha.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that — notably it never says which direction the toggle moves, what state results, whether it is idempotent in practice, or whether a reload is required.

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 tight sentence with no filler, and the operation is front-loaded. It is terse to the point of under-specification, but nothing in it is wasteful.

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

Completeness2/5

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

This is a mutating tool with no output schema and no description of the resulting state or how a caller controls the toggle direction (there is no boolean parameter). For a state-changing operation that flips an unknown current value, the description leaves the agent unable to predict the outcome.

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% for both parameters (id, path), so the schema carries the parameter documentation and the baseline is 3. The description adds no meaning about how 'path' relates to the site root the tool modifies.

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

Purpose4/5

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

States a specific verb ('toggle') and a specific resource ('.user.ini cross-site protection for a site'), so an agent knows the operation domain. It stops short of explicitly distinguishing itself from the read-side sibling 'site_dir_userini', which is left to the name pattern to convey.

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?

No guidance on when to use this versus 'site_dir_userini' or 'site_get_config', and no mention of prerequisites (e.g. whether the site must be running). The agent must infer everything from the name.

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