Skip to main content
Glama
Sign In

DropTheHassle

by io.github.bosmdavid-gif
OverviewDiscussionsAdmin

Connect domain

connect_domain
Idempotent

(needs account token) Attaches a domain registered at another registrar to a site. Nothing is transferred or bought. The reply includes the A record and the TXT ownership record to set at that registrar. On a site that already has a domain, the name is an extra that redirects (301) to the main one. A repeat with the same domain re-checks whether the name points here. Does not charge.

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": {
      "site": "<site>",
      "domain": "<domain>"
    },
    "name": "connect_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe address of a site on this account, for example myproject.dropthehassle.app.
domainYesThe domain, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"The address of a site on this account (from list_sites)."New value: +"The address of a site on this account, for example myproject.dropthehassle.app."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: '(needs account token)' flags an auth prerequisite, 'Does not charge' rules out billing, and the 301-redirect and re-check semantics explain what actually happens on repeat or multi-domain sites. This is exactly the kind of detail openWorldHint/destructiveHint cannot convey.

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?

Five short, front-loaded sentences with no filler; the auth note is prefixed so it is seen first, and each sentence carries a distinct fact (scope, non-transfer, response contents, redirect behavior, idempotency, cost).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing the return payload (A record and TXT ownership record), and it covers cost, auth, idempotency, and multi-domain behavior. Nothing an agent needs before calling is missing.

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 description coverage is 100%, so both parameters are already documented with examples in the schema. The description implies the site/domain relationship but adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ('Attaches a domain registered at another registrar to a site') and immediately scopes it by negation ('Nothing is transferred or bought'), which separates it from transfer_domain_out, point_domain, and search_domain without the agent needing to open another 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?

Gives clear triggering context (domain held at another registrar) plus two edge-case behaviors: on a site that already has a domain the name becomes a 301 redirect, and a repeat call re-checks ownership rather than duplicating. It never names a sibling alternative by name, so routing is inferred rather than explicit.

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