Skip to main content
Glama
Sign In
bearded-giant

spaceship-mcp

by bearded-giant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create SRV Record

create_srv_record
DestructiveIdempotent

Creates an SRV record to route service traffic for a domain, replacing any existing SRV records with the same name. Check existing DNS records first to avoid overwriting them.

Instructions

Create an SRV record (service locator) for a domain. WARNING: This replaces ALL existing SRV records with the same name — previous SRV 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
nameYesService name (e.g. "_autodiscover._tcp")
portYesPort number
domainYesThe domain name
targetYesTarget hostname (e.g. "autodiscover.example.com")
weightYesWeight for load balancing
priorityYesPriority (lower = higher priority)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description details that records are overwritten, not merged, adding specific behavioral context. No contradiction with annotations.

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, no superfluous text. First sentence states purpose, second delivers critical warning. Highly efficient.

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?

Covers the destructive behavior and prerequisite check. However, does not specify return value or confirmation of success, which would be helpful given no output schema.

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?

All 7 parameters have schema descriptions (100% coverage). The tool description adds no additional meaning; baseline 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?

Clearly states 'Create an SRV record (service locator) for a domain' with specific verb and resource. Distinguishes from sibling record creation tools by name and type.

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?

Explicitly warns that the tool replaces ALL existing SRV records with the same name and advises using list_dns_records first to check. Provides clear when-not-to-use and alternative.

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