Skip to main content
Glama

Order webspace

webspace_create
Destructive

Provision a paid webspace. Charges the user's mandate. Returns {orderId, orderToken, status}.

For a one-shot free trial site, use webspace_claim_free instead. See the pricing docs to estimate cost, or pick the smallest plan that fits and call webspace_upgrade later.

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": {
      "diskGb": "<diskGb>",
      "databases": "<databases>"
    },
    "name": "webspace_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmsNoPre-installed CMS (default: STATIC = no CMS)
diskGbYesDisk space in GB (10-500)
intervalNoBilling interval; yearly typically gets a discountmonthly
databasesYesNumber of MariaDB databases (10-50)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the crucial fact that the call charges the user's mandate — a real financial side effect not derivable from annotations. It also discloses the return shape ({orderId, orderToken, status}), which matters since there is no output schema. It stops short of stating idempotency or whether a duplicate call double-charges.

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: the action plus side effect first, the return shape second, the alternative routing third. No filler, and the most consequential information (it costs money) is front-loaded in sentence two.

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 paid, irreversible-feeling mutation with four parameters and no output schema, the definition covers cost, return fields, and the cheaper alternatives. The remaining gap is procedural safety: nothing about double-submission, retry behavior, or precondition failures, which an agent committing a charge would want.

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% with enums and range bounds already documented for diskGb, databases, cms, and interval. The description adds only an indirect sizing heuristic ("pick the smallest plan") and no new meaning about interval/plan interactions. Baseline 3 given the schema does the heavy lifting.

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?

States a specific verb and resource ("Provision a paid webspace") and immediately distinguishes it from the free-trial path by naming `webspace_claim_free`. An agent can tell this apart from `webspace_upgrade` and `webspace_claim_free` 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 Guidelines5/5

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

Explicitly routes the agent: use `webspace_claim_free` for a one-shot free trial, and use `webspace_upgrade` later if the smallest plan turns out too small. It also points to pricing docs for cost estimation before committing to a paid order.

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.