Skip to main content
Glama

ss_personal_ns_delete

Delete a personal nameserver from a domain to remove custom name server configuration.

Instructions

Delete a personal nameserver from a domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain name
hostYesHost name to delete (e.g. ns1)
Behavior2/5

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

No annotations provided, so description bears full burden. It omits crucial behavioral traits: consequences (e.g., DNS record removal), reversibility, or required permissions for deletion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, no wasted words, but may be too terse to be fully informative. Front-loaded well.

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?

Lacks output schema and annotations; does not describe return value or effects, insufficient for a deletion tool with two parameters.

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 covers both parameters (domain, host) with descriptions, so baseline is 3. Description adds no further meaning beyond schema.

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 uses specific verb 'Delete' and resource 'personal nameserver from a domain', clearly distinguishing it from sibling tools like get, list, update.

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

Usage Guidelines2/5

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

No guidance on when to use or alternatives; for example, it does not differentiate from ss_dns_delete or mention prerequisites like domain ownership.

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/hlebtkachenko/spaceship-mcp'

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