Skip to main content
Glama
Sign In
bearded-giant

spaceship-mcp

by bearded-giant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create A Record

create_a_record
DestructiveIdempotent

Creates an IPv4 A record for a domain and overwrites any existing A records with the same name; check existing DNS records first to avoid unintended replacement.

Instructions

Create an A record (IPv4 address) for a domain. WARNING: This replaces ALL existing A records with the same name — previous A records for this name will be overwritten, not merged. Use list_dns_records first to check for existing records.

Input Schema

NameRequiredDescriptionDefault
ttlNoTTL in seconds
nameYesRecord name (subdomain, use "@" for root)
domainYesThe domain name
addressYesIPv4 address (e.g. "192.0.2.1")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Despite annotations already indicating destructive behavior, the description adds critical context: 'replaces ALL existing A records with the same name — previous A records for this name will be overwritten, not merged.' This goes beyond annotations to clarify the exact 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?

Two sentences with a front-loaded warning. Every word serves a purpose, no redundancy.

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 high schema coverage, annotations, and no output schema, the description is complete. It covers the tool's purpose, usage context, and destructive behavior without omission.

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 all parameters described. The description does not add additional parameter details, but the schema already provides adequate meaning for each field.

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 'Create an A record (IPv4 address) for a domain.' It specifies the record type and protocol, distinguishing it from sibling DNS 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?

The description provides explicit usage guidance: 'Use list_dns_records first to check for existing records.' It warns about destructive behavior, helping the agent decide when to use this tool vs. alternatives.

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