Skip to main content
Glama

Remove launch page address

launchpad_domain_remove
DestructiveIdempotent

Stop showing the launch page at its own address. The hollerpost.com address keeps working. Ask for confirmation first; requires confirm: true. Requires API key scope: draft.

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": {
      "confirm": "<confirm>"
    },
    "name": "launchpad_domain_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYestrue only after the person approved removing the address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds real context beyond them: the hollerpost.com address survives the removal, a confirmation gate is required, and the API key scope is 'draft'. That is meaningful pre-execution information for a destructive call; only the fate of existing links or the return response is unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Four short sentences, each carrying distinct information: effect, retained address, confirmation requirement, and auth scope. The effect is front-loaded and nothing is repeated. Slightly choppy as fragments, but every sentence earns its place.

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 one-parameter destructive tool with no output schema, the definition covers what changes, what persists, the confirmation prerequisite, and the required scope — enough for an agent to call it correctly. Only the downstream effect on existing page links or verification state is left unstated.

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 100% and the single confirm parameter is documented as a const true, so the baseline is 3. The description adds workflow meaning by instructing the agent to ask the person for approval before passing confirm: true, which frames the parameter as a human-in-the-loop gate rather than a formality.

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 states a specific verb and resource: 'Stop showing the launch page at its own address,' which is clearly the launchpad-scoped counterpart to the generic domain_remove and to launchpad_domain_set. It also explains the resulting state (the hollerpost.com address keeps working), so an agent can distinguish the effect from siblings 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 Guidelines3/5

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

Usage is implied by the outcome statement: if the launch page should still be reachable at hollerpost.com but not at its custom address, this is the tool. However, no alternative is named — not launchpad_set_offline nor domain_remove — and there is no explicit when-not guidance, so the agent must infer routing from sibling names.

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.

Resources