Skip to main content
Glama

Sitey — free subdomains

by my.sitey
OverviewDiscussionsAdmin

delete_subdomain

Permanently delete a subdomain DNS record you own. The subdomain will stop resolving immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesRoot domain (e.g. 'sitey.my')
subdomainYesSubdomain name (e.g. 'demo')
owner_tokenNoThe owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creating without one mints a new one and returns it once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Root domain (e.g. 'sitey.one')"New value: +"Root domain (e.g. 'sitey.my')"
    • addedInput schema / properties / owner_token
      Added value: +{
+  "description": "The owner token you were given when you created the record (starts with anon_). Omit it only if you have an API key, or if the record predates tokens and was claimed from this same IP address. Creating without one mints a new one and returns it once.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It clearly discloses the destructive nature ('permanently delete'), the immediate consequence ('will stop resolving immediately'), and implicitly warns about irreversibility. It does not mention authorization or side effects on related records, but the core hidden behavior is well covered.

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 short sentences with no wasted words. The key facts—permanence and immediate resolution impact—are front-loaded, and every phrase earns its place.

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?

For a simple destructive tool with no output schema, the description gives the essential outcome and permanence. It does not explain return behavior, but the required parameters are already fully documented in the schema, so the agent has enough to invoke it correctly.

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 description coverage is 100%, so the schema fully documents all parameters. The description adds no additional parameter-level meaning, which is acceptable but not above the baseline.

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 states a specific verb ('delete') and a specific resource ('subdomain DNS record'), and clarifies ownership. It is clearly distinguishable from the sibling delete_txt_record, which targets a different record type.

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?

There is no guidance about when to use this tool versus alternatives such as delete_txt_record, or when deletion might be inappropriate. The phrase 'you own' implies a prerequisite but does not explicitly tell the agent how to choose this tool.

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

All Sitey — free subdomains toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources