Skip to main content
Glama

DropTheHassle

by io.github.bosmdavid-gif
OverviewDiscussionsAdmin

Point domain

point_domain
DestructiveIdempotent

(needs account token) Moves a domain that is already on the account to another of its sites, or back onto a site it was split from. Does not buy a name and does not edit DNS at another registrar. confirm=true applies the move. Does not charge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesA domain already on this account.
confirmYesTrue applies the change. False leaves it unchanged and the reply describes what would change.
to_siteYesThe address of the site to point it at, for example myproject.dropthehassle.app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"true ONLY after the human explicitly said yes to moving this domain."New value: +"True applies the change. False leaves it unchanged and the reply describes what would change."
    • changedInput schema / properties / to_site / description
      Previous value: -"The address of the site to point it at, e.g. myproject.dropthehassle.app (from list_sites)."New value: +"The address of the site to point it at, for example myproject.dropthehassle.app."
  2. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "true ONLY after the human explicitly said yes to moving this domain.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "domain",
-  "to_site"
-]New value: +[
+  "domain",
+  "to_site",
+  "confirm"
+]
  3. Changed3 schema fields changed
    • addedInput schema / properties / to_site
      Added value: +{
+  "description": "The address of the site to point it at, e.g. myproject.dropthehassle.app (from list_sites).",
+  "type": "string"
+}
    • removedInput schema / properties / to_site_id
      Removed value: -{
-  "description": "The site to point it at (from list_sites).",
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "domain",
-  "to_site_id"
-]New value: +[
+  "domain",
+  "to_site"
+]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false. The description adds real value beyond those: the '(needs account token)' auth requirement, the dry-run semantics of confirm, and the fact that it 'Does not charge' — pre-empting a billing assumption. It doesn't spell out what happens to the domain's state on the old site, keeping 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.

Conciseness4/5

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

Four short sentences, front-loaded with the auth note and core purpose, then scope exclusions, then confirm behavior and cost. Every sentence carries signal; only the confirm restatement borders on redundancy with the schema.

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 mutation tool with no output schema, it covers auth, dry-run, cost, and scope — the essentials an agent needs to call it correctly. It stops short of describing post-move effects on the previous site's content or explicit reversibility guarantees.

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%, so all three parameters are already documented in the schema. The description restates the confirm=true apply behavior (already in the schema) and adds only marginal semantics, like the 'back onto a site it was split from' framing for to_site. Baseline 3 is appropriate.

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 (move/point) and resource (domain) plus scope: 'a domain that is already on the account to another of its sites, or back onto a site it was split from.' This separates it from purchasing and from external-registrar DNS work, though it doesn't name sibling tools like split_domain or connect_domain outright.

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?

Clearly frames when to use it (re-homing an already-owned domain between sites, including reversing a split) and gives exclusions ('Does not buy a name and does not edit DNS at another registrar'), which implicitly routes buyers/DNS tasks elsewhere. No explicit sibling-tool alternative is named, so not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All DropTheHassle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources