Skip to main content
Glama

SoFast

Change a site's address

change_site_address
DestructiveIdempotent

Moves the site to .sofast.website. The old address stops working at once. A site's address can be changed once a day. Custom domains are unaffected.

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": "<site>",
      "subdomain": "<subdomain>"
    },
    "name": "change_site_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its numeric id, its address (name.sofast.website or a custom domain) or its URL.
subdomainYesLowercase letters, digits and hyphens, 3 to 63 characters.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), it discloses the real consequence that the old address stops working immediately and a rate limit of one change per day. It also scopes the operation, noting custom domains are unaffected, which an agent cannot learn from the structured fields.

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?

Four short sentences, front-loaded with the primary effect, then consequence, then rate limit, then scope. Every sentence carries information an agent needs before calling.

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 destructive, non-read-only mutation with no output schema, the description covers consequence, frequency limit, and scope well. It does not mention permissions/ownership requirements or whether the site serves during the move, which are minor residual gaps.

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%, so both parameters are already documented with format rules. The description only adds that the supplied subdomain composes the resulting '<subdomain>.sofast.website' address, a marginal but genuine clarification, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and effect: it moves the site to '<subdomain>.sofast.website', which tells an agent exactly what changes. However, it offers no differentiation from the confusingly similar sibling rename_site, so an agent must infer which one to pick.

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

Usage Guidelines3/5

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

Usage is implied (use this when you need a site's address changed) and a key constraint is given — once per day, custom domains unaffected — but there is no explicit guidance about when to prefer this over rename_site or what prerequisites exist.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources