Skip to main content
Glama

Upgrade webspace

webspace_upgrade
Destructive

Increase diskGb and/or databases on a paid webspace. Errors on downgrade or on free-tier sites. Creates a pro-rated payment via your saved mandate; the new limits apply after payment confirmation. You MUST set confirm to 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>",
      "confirm": "<confirm>"
    },
    "name": "webspace_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
diskGbNo
confirmYesMust be true to confirm this billable operation
databasesNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, and the description adds substantial context on top: the operation is billable, it creates a pro-rated payment through a saved mandate, new limits only take effect after payment confirmation, and confirm must be true. These are the exact side-effect and authorization details an agent needs before committing to a charge.

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 core action, then constraints, then billing consequence. Nothing is redundant with the title or schema, and the mandatory confirm instruction is placed last as an action prompt.

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 billable mutation with no output schema, the description covers the effect, the billing mechanism, timing of the change, and the guard conditions. It omits what is returned or how a partially failed payment surfaces, which would round out the picture but is not essential to calling it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the two undocumented parameters (diskGb, databases) are precisely the ones the description clarifies — it says either or both may be increased, implying optionality, and that decreases are rejected despite the schema's bare min/max bounds. The id and confirm meanings are left to the schema, which documents them adequately.

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 first sentence names a specific verb (increase) plus the exact resource (a paid webspace) and the two fields affected (diskGb, databases). It immediately distinguishes itself from sibling mutations like webspace_cancel or webspace_delete, and an agent can identify the operation without opening the 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?

It states clear preconditions and exclusions: only paid webspaces, and calls fail on downgrade attempts or free-tier sites. It does not explicitly route to an alternative (e.g. a VPS equivalent) or say what to do when an upgrade is rejected, so it falls short of full when/when-not/alternative coverage.

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.