Skip to main content
Glama
Sign In
bearded-giant

spaceship-mcp

by bearded-giant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Personal Nameserver

delete_personal_nameserver
Destructive

Deletes a personal nameserver host and its registry glue record for a domain; verify it isn't actively used, as removal can cause DNS downtime.

Instructions

Delete a personal nameserver host from a domain. This removes the glue record at the registry. WARNING: If this nameserver is actively used by any domain, those domains will lose DNS resolution and experience downtime. Always confirm with the user before calling this tool.

Input Schema

NameRequiredDescriptionDefault
hostYesThe nameserver hostname to delete (e.g. "ns1.yourdomain.com").
domainYesThe parent domain name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses destructive behavior (removes glue record, causes downtime if in use) beyond the destructiveHint annotation. It warns about side effects and user confirmation, aligning with annotations and adding value.

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?

The description is concise: two sentences and a warning. It is front-loaded with the action, then provides crucial caution. Every sentence adds value.

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?

Parameters are fully described in schema, annotations cover destructive behavior, and the description adds a critical warning about DNS resolution loss. It lacks mention of return value or error states, but is complete enough for a destructive tool.

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% with clear parameter descriptions (host, domain). The tool description does not add new semantic meaning beyond what is in the schema, so baseline score of 3 is appropriate.

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 clearly states it deletes a personal nameserver host from a domain and removes the glue record at the registry. It distinguishes from sibling tools like list_personal_nameservers and update_personal_nameserver by specifying deletion.

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?

The description includes a strong WARNING about potential downtime if the nameserver is in use and instructs to always confirm with the user. It does not, however, explicitly mention when not to use it or alternative tools for related tasks, such as removing DNS records.

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

Deploy Server

Other Tools