Skip to main content
Glama

Cancel webspace

webspace_cancel
Destructive

Cancel a webspace subscription at the end of the current billing period. The webspace keeps running until the expiry date and is then removed. 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>",
      "confirm": "<confirm>"
    },
    "name": "webspace_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webspace ID
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description adds genuinely non-redundant behavior: the resource keeps running until the expiry date and is only then removed, so destruction is deferred. It also surfaces the required confirm: true gate, which is not obvious from the annotation alone. It stops short of noting reversibility via an uncancel path or ownership/permission requirements.

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 and its timing, followed by the consequence and the call requirement. No filler or restatement of the title.

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 two-parameter mutation with annotations and no output schema, the description covers effect, timing, and the confirm gate. A note on whether the cancellation can be reversed (an uncancel tool exists among siblings) and any ownership prerequisites would close the remaining gap.

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 50%: id is documented in the schema but confirm carries only const:true with no prose. The description compensates by explicitly stating "Requires confirm: true", telling the agent the call will be rejected without it. It adds no detail about the ID format, though the schema already supplies the 24-hex pattern.

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 and resource ("Cancel a webspace subscription") and pins the timing ("at the end of the current billing period"), which implicitly separates it from an immediate-delete sibling. It never names an alternative such as webspace_delete or webspace_uncancel, so differentiation is left partly to inference.

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

Usage Guidelines3/5

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

The deferred effect gives an agent enough to infer this is the scheduled-cancellation path rather than a hard delete, and the confirm requirement is stated. However, there is no explicit 'use this instead of X' guidance or precondition about when cancellation is appropriate.

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.