Skip to main content
Glama

Sitey — free subdomains

by my.sitey
OverviewDiscussionsAdmin

create_subdomain

Create a new DNS record for a subdomain. Supports A records (IP address), CNAME records (hostname) and REDIRECT records (an https:// URL — visitors to the name are sent there with a 301). Example: create demo.sitey.my pointing to 1.2.3.4. No account, API key or signup is needed. The target does not have to be serving yet: claim the name first and deploy to it second if that is your order. The result carries reachable:false when nothing answered, and the record is created either way. If you send no owner_token, the result carries a new one under 'owner_token' — save it, it is shown once and is the only way to change or delete this record later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesRecord type. REDIRECT answers every visit with a 301 to the URL in value.
valueYesRecord value: an IPv4 address for A, a hostname for CNAME, an absolute https:// URL for REDIRECT (http:// is refused, and so is a URL under one of this service's own roots).
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. Changed3 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Record type"New value: +"Record type. REDIRECT answers every visit with a 301 to the URL in value."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "A",
-  "CNAME"
-]New value: +[
+  "A",
+  "CNAME",
+  "REDIRECT"
+]
    • changedInput schema / properties / value / description
      Previous value: -"Record value (IP for A, hostname for CNAME)"New value: +"Record value: an IPv4 address for A, a hostname for CNAME, an absolute https:// URL for REDIRECT (http:// is refused, and so is a URL under one of this service's own roots)."
  2. 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"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well. It discloses that the record is created even when nothing answers, that the result carries reachable:false in that case, and that omitting owner_token mints a new one shown only once and required for later changes or deletion. This is rich, honest behavioral disclosure.

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?

The description is front-loaded with the core purpose and record types, followed by a useful example and then behavioral notes. It is a bit long and slightly redundant with the schema's owner_token explanation, but every sentence earns its place for a tool with nuanced token and reachability behavior.

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?

For a 5-parameter tool with no annotations and no output schema, the description is remarkably complete. It covers record types, request format, the no-auth property, the reachable:false behavior, and the one-time owner_token. An agent has what it needs to invoke the tool correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds a concrete example mapping subdomain, domain, and value, and reinforces the token semantics with emphasis that it is shown once and is the only way to modify/delete. This is meaningful added value beyond the 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?

The description opens with a specific verb and resource ('Create a new DNS record for a subdomain'), enumerates the supported record types (A, CNAME, REDIRECT), and gives a concrete example. This clearly distinguishes it from sibling tools like create_txt_record.

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

Usage Guidelines4/5

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

It gives clear contextual guidance: no account/API key/signup needed, and the target does not need to be serving yet, so users can 'claim the name first and deploy to it second.' It does not explicitly name alternatives or say when not to use this tool, but the context is strong enough to infer appropriate use.

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