Skip to main content
Glama

Sitey — free subdomains

by my.sitey
OverviewDiscussionsAdmin

renew_subdomain

Extend a subdomain you own before it expires. Subdomains are lent for a period, not given: agent-created records last one month and user records three. Nothing emails an agent, so read expires_at from list_subdomains and call this before that date. One call resets the clock from today. Renewal only opens in the last two weeks before expires_at — an earlier call is refused and tells you the date it opens.

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

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It explains that subdomains are lent, not given, with different durations for agent-created vs user records. It discloses that one call resets the clock from today, and that renewal opens only in the last two weeks. It also notes that no emails are sent, so the agent must read expires_at. This fully informs the agent of operational behavior.

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 compact and front-loaded with the core purpose. Each sentence adds essential context: the lending concept, the renewal window, and the token requirement. There is no redundancy; every sentence earns its place. It's appropriately sized for the complexity.

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?

The description is complete for a renewal tool. It covers when to use, how to use (read expires_at from list_subdomains), constraints (last two weeks), and side effects (resets clock). There is no output schema, but the description could mention the response (e.g., new expires_at) to be fully complete, but given the context signals (no output schema) and the richness of the description, this gap is minor. Overall, an agent has everything needed to call 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 already documents all three parameters with examples. The description adds context about the owner_token's role ('The owner token you were given when you created the record') and when it can be omitted, which is beyond the schema. However, it doesn't explain the domain and subdomain parameters beyond what the schema provides. Since coverage is high, baseline 3 is appropriate.

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 clearly states the tool's purpose: to extend a subdomain before it expires, with a specific verb (renew) and resource (subdomain). It differentiates from siblings like create_subdomain and list_subdomains by focusing on renewal semantics. The phrase 'Extend a subdomain you own before it expires' is precise and actionable.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: check expires_at from list_subdomains and call before that date. It also clarifies when not to use: 'Renewal only opens in the last two weeks before expires_at — an earlier call is refused.' It references the sibling list_subdomains, providing clear context for selection.

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