Skip to main content
Glama
mattcollins

Spaceship MCP Server

by mattcollins

create_txt_record

Create a TXT record for a domain to add text-based DNS entries such as SPF, DKIM, or verification tokens. Specify domain, subdomain, value, and optional TTL.

Instructions

Create a TXT record (text data) for a domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNoTime to live in seconds (optional)
nameYesThe record name (subdomain, use "@" for root domain)
valueYesThe text value (e.g., "v=spf1 include:example.com -all")
domainYesThe domain name
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It merely states 'Create a TXT record' without disclosing any side effects, idempotency, permissions, or irreversibility.

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 a single sentence of 10 words, immediately stating the action and object. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite full schema coverage, the description lacks behavioral context and usage guidance. For a mutation tool with no annotations or output schema, this is insufficient to fully guide an agent.

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?

The input schema provides complete descriptions for all four parameters (100% coverage), so the description adds no additional parameter semantics. Baseline of 3 applies.

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 uses the specific verb 'Create' with the resource 'TXT record' and clarifies 'text data', clearly distinguishing it from sibling tools like create_a_record or create_cname_record.

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

Usage Guidelines3/5

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

The description implies usage for TXT records but does not explicitly state when to choose this over create_dns_record or other create_* tools. No exclusions or alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattcollins/spaceship-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server