Skip to main content
Glama

SoFast

Create a site

create_site

Creates a new site at .sofast.website and publishes its first version, within the account's plan. With upload_id, publishes those uploaded files. With upload set to link, returns a one-time upload command instead. If the first version is refused, the site is not kept.

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": {
      "title": "<title>",
      "subdomain": "<subdomain>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesThe site's name, shown in the Sofast dashboard.
uploadNolink: return an upload command rather than publishing an upload_id.
subdomainYesLowercase letters, digits and hyphens, 3 to 63 characters.
upload_idNoThe upload_id returned by upload_files, whose files become the site's content.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description does add genuinely useful context beyond them: the account plan constraint and, notably, the atomicity guarantee that a refused first version means the site is not kept. However, no idempotency note and no mention of what happens when a subdomain is already taken are provided.

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, each carrying distinct information: what is created, the two optional branches, and the failure/rollback semantics. The core operation is front-loaded and nothing is repeated or wasted.

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 create tool with no output schema, the description covers behavior, modes, and failure semantics well. The remaining gap is the return value in the default path (e.g., whether a site id is returned), which an agent relying solely on this text cannot know, though the 'link' branch return is described.

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 the schema already documents all four parameters, including the upload_id linkage and subdomain format. The description adds the mutual-exclusivity relationship between upload_id and upload='link' and clarifies that the subdomain forms the public URL. That is useful but marginal over structured fields; baseline 3 applies.

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 ('Creates a new site at <subdomain>.sofast.website') and adds an important side effect ('publishes its first version'), which implicitly separates it from the sibling publish_site that handles later versions. An agent can identify the operation and its scope without inspecting the schema.

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 spells out the three invocation modes: default with upload_id, upload set to 'link' to get an upload command instead, and plain creation. That is real conditional guidance for choosing a path. It stops short of explicitly stating prerequisites or when to use upload_files first, so it is not a full when/when-not/alternatives statement.

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