Skip to main content
Glama

Sitey — free subdomains

by my.sitey
OverviewDiscussionsAdmin

update_subdomain

Update the DNS record value of a subdomain you own. For example, change the IP address that demo.sitey.my points to. The new target does not have to be serving yet; the result carries reachable:false when nothing answered, and the record is moved either way.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesNew record value
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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it reveals that the target need not be live, that reachable:false appears in the result, and that the record is updated regardless. This goes beyond what the schema conveys.

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?

Three sentences, all earning their place: the first states the action, the second gives a concrete example, and the third discloses non-obvious behavior. The main point is front-loaded with no wasted words.

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?

Given there is no output schema and no annotations, the description covers the key side effect and result signal (reachable:false). The owner-token nuance is fully handled by the schema, so nothing critical is missing for a correct call.

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 baseline is 3. The description adds a concrete example (IP address for value, demo.sitey.my for subdomain/domain) but does not materially expand parameter meaning 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 states a specific verb and resource ('Update the DNS record value of a subdomain you own') and includes a concrete example that makes the operation unmistakable. This clearly differentiates the tool from create/delete/list siblings.

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?

The description provides clear context for when to use the tool: updating an existing, owned subdomain's DNS target. It does not explicitly name alternatives or exclusions, but the operation is unambiguous enough that an agent can select it correctly.

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