Skip to main content
Glama
Sign In

Sitelas

by com.sitelas
OverviewDiscussionsAdmin

Change the site's web address

change_site_address
DestructiveIdempotent

Rename a site's Sitelas address ({subdomain}.sitelas.com) — the same change as the dashboard's site settings. The old address keeps working: it 301-redirects to the new one, and stays reserved for this site. The preview address moves too (old preview links stop working), so share the new one. Rules: 1–63 lowercase letters, digits and hyphens; not a name another site uses or used, nor a reserved word (www, admin, preview-…). A custom domain is separate and unaffected — that is set_custom_domain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>",
      "new_subdomain": "<new_subdomain>"
    },
    "name": "change_site_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site UUID.
new_subdomainYesThe new address label, e.g. 'joes-bakery' for joes-bakery.sitelas.com: 1–63 lowercase letters, digits and hyphens, starting and ending with a letter or digit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: the old address 301-redirects and stays reserved, the preview address migrates and old preview links break, and the change is scoped to the Sitelas subdomain only. This is exactly the side-effect detail an agent needs before invoking a destructiveHint=true mutation.

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?

Front-loaded with the action and its consequence, then rules, then the sibling pointer — a sensible order with no filler sentences. Minor redundancy between the description's character rules and the schema's identical constraints.

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 two-parameter mutation with no output schema, the description covers what changes, what breaks, what is preserved, validity rules, and the sibling alternative. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the new_subdomain description already carries the character rules, so the description mostly repeats structured data. It adds the useful note that the name must not collide with a name another site used, nor a reserved word (www, admin, preview-…), which is beyond the schema; site_id is left to 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?

Names a specific verb (rename) and resource (the site's Sitelas address, {subdomain}.sitelas.com), and explicitly distinguishes the operation from set_custom_domain. An agent can tell instantly what changes and what does not.

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?

States the equivalence to the dashboard's site settings and explicitly routes custom-domain work to set_custom_domain, so the main alternative is covered. It does not discuss other plausible paths (e.g. creating a new site versus renaming), but for this tool family the guidance is clear.

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

All Sitelas 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