Skip to main content
Glama
Sign In
bearded-giant

spaceship-mcp

by bearded-giant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create NS Record

create_ns_record
DestructiveIdempotent

Creates an NS record to delegate a subdomain to a nameserver; it replaces existing NS records with the same name, so check records first.

Instructions

Create an NS record (nameserver delegation) for a domain. WARNING: This replaces ALL existing NS records with the same name — previous NS records for this name will be overwritten, not merged. Incorrect NS records can break DNS resolution for delegated subdomains. Use list_dns_records first to check for existing records.

Input Schema

NameRequiredDescriptionDefault
ttlNoTTL in seconds
nameYesRecord name (subdomain to delegate)
domainYesThe domain name
nameserverYesNameserver hostname (e.g. "ns1.example.com")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Description goes beyond annotations by detailing the destructive behavior (replaces all existing NS records with the same name) and potential DNS impact, adding critical behavioral context.

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?

Four tight sentences with no waste: front-loaded purpose, warnings, and actionable advice. Every sentence earns its place.

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?

Given full schema coverage and rich annotations, the description covers the essential behavior, destructive nature, prerequisites, and consequences comprehensively.

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 has high coverage (100%), so baseline is 3. Description adds behavioral context for the 'name' parameter by explaining it determines which records are replaced, beyond the schema's description.

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?

Description clearly states 'Create an NS record (nameserver delegation) for a domain', specifying the exact resource and action. It uniquely identifies this tool among many sibling record creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit warnings about overwriting existing NS records and suggests using list_dns_records first to check, offering clear when-to-use and when-to-avoid guidance.

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