Skip to main content
Glama

Install CMS on webspace

webspace_install_cms
Destructive

Install (or reinstall) a CMS on a webspace. WIPES the existing docroot and resets the database — requires confirm:true. Returns immediately with a jobId; install runs in the background. Poll webspace_get to see when cms updates.

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>",
      "cms": "<cms>",
      "confirm": "<confirm>"
    },
    "name": "webspace_install_cms"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
cmsYesCMS to install. STATIC scaffolds a placeholder index.html with no database.
confirmYesMust be true to confirm — the existing docroot will be wiped and the database reset.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description names exactly what is destroyed (existing docroot) and what is reset (the database), plus the required confirmation flag. It also discloses asynchronous behavior: the call returns immediately with a jobId and completion is observed via webspace_get. This is precisely the extra context 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Highly front-loaded and free of filler: three short sentences covering action, destruction, and async follow-up. The only inefficiency is that confirm:true is stated twice in effect (description and schema), but that is a minor redundancy.

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

Completeness5/5

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

With no output schema, the description still tells the agent what the call returns (a jobId) and how to observe completion, which is the essential missing piece. For a three-parameter destructive tool, nothing an agent needs in order to invoke it safely is absent.

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%, so id, cms, and confirm are already fully documented, including the STATIC enum meaning. The description adds only the reinstall implication and the confirm requirement, which the schema already states, so it earns the baseline rather than more.

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?

The description opens with a specific verb and resource: 'Install (or reinstall) a CMS on a webspace.' It also covers the reinstall case explicitly, so an agent can tell it apart from read-oriented siblings such as webspace_get without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly states the context for use (fresh install or reinstall), the precondition confirm:true, and the follow-up step of polling webspace_get for the cms field. It does not explicitly warn against use on webspaces that should be preserved, but the destructive framing makes that implication clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.