Skip to main content
Glama

Set webspace PHP version

webspace_set_php
Destructive

Change the PHP version for a webspace. Restarts OLS gracefully. Site code may break under the new PHP version — requires confirm:true.

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>",
      "version": "<version>",
      "confirm": "<confirm>"
    },
    "name": "webspace_set_php"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
confirmYesMust be true to confirm — a PHP version change can break sites incompatible with the new version.
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real context beyond them: the OLS restart is graceful, and site code may break under the new version. The confirmation gate is spelled out as a safety mechanism; it doesn't discuss rollback or expected downtime, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action, then the side effect, then the risk and required flag. Nothing is redundant or padded.

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 3-parameter destructive mutation with annotations and no output schema, the description covers the action, side effect, risk, and confirmation requirement. The only gap is that the 'version' parameter is left entirely to its enum without explanation.

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 67%, so the schema already documents 'id' and 'confirm'. The description repeats the confirm requirement but adds no meaning about the 'version' parameter, whose enum values (8.2–8.5) and lack of a description mean the agent gets no guidance on which versions exist or how to choose one.

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 ('Change the PHP version for a webspace') and names the exact setting being mutated. No sibling tool touches PHP versions, so an agent can route here unambiguously.

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?

It states the operation applies to a webspace's PHP version and that 'confirm:true' is required, which is a concrete precondition for invoking it. It stops short of naming when not to use it or pointing at any alternative, but no sibling performs a comparable action.

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.