Skip to main content
Glama

SoFast

Publish a site

publish_site
Destructive

Publishes uploaded files as a new version of an existing site, replacing what it serves. The previous version stays available for restoring from the Sofast dashboard.

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>",
      "upload_id": "<upload_id>"
    },
    "name": "publish_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its numeric id, its address (name.sofast.website or a custom domain) or its URL.
upload_idYesThe 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
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The description earns credit for adding real context beyond that: it explains what is destroyed ('replacing what it serves') and that the previous version remains recoverable via the Sofast dashboard, which meaningfully reduces the perceived risk of a destructive call.

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?

Two short sentences with no filler. The replace semantics are front-loaded, and the recovery assurance follows immediately where it is most needed.

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 mutation with annotations covering safety and a fully described schema, the description is nearly complete. The one remaining gap is whether publishing is synchronous or must be polled via get_site_status, which the agent would need to know to confirm success.

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 fully documented, including the accepted site identifier forms and that upload_id comes from upload_files. The description adds no syntax, format, or edge-case detail beyond restating that the site must already exist and content comes from an upload, so 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?

States a specific verb and resource ('Publishes uploaded files as a new version of an existing site') plus the resulting effect ('replacing what it serves'). The word 'existing' implicitly separates it from create_site, and the reference to 'uploaded files' ties it to upload_files, so an agent can place it in the workflow without opening 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 Guidelines3/5

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

Usage context is implied rather than stated: it operates on an existing site using a prior upload, which rules out create_site and upload_files by definition. However, there is no explicit when-to-use guidance, no mention of what to do first (upload_files), and no pointer to siblings like get_site_status for verifying the result.

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