Skip to main content
Glama

DropTheHassle

by io.github.bosmdavid-gif
OverviewDiscussionsAdmin

Choose link

choose_link
Destructive

Renames a site's link to name.dropthehassle.app. The previous link redirects to the new one. Without an account, claim_url or site_token identifies the unclaimed site. With an account, site identifies it. confirm=true applies the new name. Does not charge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe label only, e.g. "myproject" for myproject.dropthehassle.app.
siteNoWith an account: the address of the site to rename, for example myproject.dropthehassle.app.
confirmYesTrue applies the change. False leaves it unchanged and the reply describes what would change.
claim_urlNoThe claim link from an unclaimed deploy. The part after # is the secret.
site_tokenNoWithout an account: that site's token, from the deploy reply. A site token sent as Bearer works too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / claim_url / description
      Previous value: -"Without an account: the claim link deploy_site returned (the part after # is the secret)."New value: +"The claim link from an unclaimed deploy. The part after # is the secret."
    • changedInput schema / properties / confirm / description
      Previous value: -"true ONLY after the human owner explicitly approved this exact name."New value: +"True applies the change. False leaves it unchanged and the reply describes what would change."
    • changedInput schema / properties / site / description
      Previous value: -"With an account: the address of the site to rename (from list_sites)."New value: +"With an account: the address of the site to rename, for example myproject.dropthehassle.app."
  2. Changed4 schema fields changed
    • addedInput schema / properties / claim_url
      Added value: +{
+  "description": "Without an account: the claim link deploy_site returned (the part after # is the secret).",
+  "type": "string"
+}
    • changedInput schema / properties / site / description
      Previous value: -"The address of the site to rename (from list_sites)."New value: +"With an account: the address of the site to rename (from list_sites)."
    • addedInput schema / properties / site_token
      Added value: +{
+  "description": "Without an account: that site's token, from the deploy reply. A site token sent as Bearer works too.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "site",
-  "name",
-  "confirm"
-]New value: +[
+  "name",
+  "confirm"
+]
  3. Changed3 schema fields changed
    • addedInput schema / properties / site
      Added value: +{
+  "description": "The address of the site to rename (from list_sites).",
+  "type": "string"
+}
    • removedInput schema / properties / site_id
      Removed value: -{
-  "description": "The site to rename (from list_sites).",
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "site_id",
-  "name",
-  "confirm"
-]New value: +[
+  "site",
+  "name",
+  "confirm"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say non-readonly, destructive, non-idempotent), the description discloses the key side effect that the previous link redirects to the new one, that the operation is free ('Does not charge'), and that confirm=false acts as a dry run whose reply describes what would change. These are exactly the behavioral facts an agent needs before invoking a destructive mutation.

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 sentences, no filler: the outcome is front-loaded, then the identifier branching, then the confirm semantics and cost note. Every sentence carries operational content and the ordering matches how an agent would reason about the call.

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?

With no output schema, the description still covers the post-call state (redirect behavior, preview reply text) and the cost dimension, which is sufficient for a 5-parameter mutation tool. It does not clarify interaction with custom or primary domains, a minor gap given the sibling set.

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%, so per-parameter meaning is already documented and the baseline is 3. The description adds orchestration logic the schema does not: the account/no-account branching that decides whether site or claim_url/site_token applies, plus the confirm-as-dry-run framing, which is value beyond the individual field docs.

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?

The description names a concrete verb and resource — renaming a site's link to name.dropthehassle.app — and specifies the resulting URL form, which is more precise than a generic 'rename' tool. It does not explicitly name or exclude the adjacent siblings (connect_domain, make_primary_domain, split_domain), so an agent must infer the boundary rather than being routed to it.

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?

It gives real selection conditions: without an account use claim_url or site_token, with an account use site, and confirm=true applies the change while false previews it. That is genuine when/how guidance for the parameters, though it stops short of naming an alternative tool or stating when this tool should not be used.

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