Skip to main content
Glama

SoFast

Get an upload command

get_upload_link
Destructive

Returns a one-time command that uploads a zip of a site's folder from a shell and publishes it as the site's new version, replacing what it serves. Valid for 15 minutes and a single upload.

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

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its numeric id, its address (name.sofast.website or a custom domain) or its URL.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavioral facts: the command expires in 15 minutes, is valid for a single upload, and replaces the currently served version. What it omits is how the returned command is meant to be invoked (arguments, expected zip path) and what happens on expiry or failure.

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 tight sentences with zero filler; the core action is front-loaded and the TTL/single-use constraint follows immediately. Every clause carries information an agent needs.

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 one-time-token tool this covers the essentials: what is returned, its lifetime, its single-use nature, and the destructive consequence of publishing over the live version. It is slightly short on operational detail — how to execute the returned command and what it expects from the zip — but no output schema is needed since the return is a command string.

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% and the single 'site' parameter is already fully documented in the schema (numeric id, address, or URL). The description adds no syntax or format guidance beyond that, so the baseline of 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?

The description uses a specific verb and resource ('Returns a one-time command that uploads a zip of a site's folder ... and publishes it'), and the phrase 'from a shell' implicitly distinguishes it from the in-API sibling upload_files. It stops short of naming that alternative, so the differentiation is inferential rather than explicit.

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 only implied: 'from a shell' suggests this is for shell-driven zipped uploads rather than direct file uploads. There is no explicit when-to-use/when-not-to-use statement and no named alternative such as upload_files or publish_site, leaving the agent to infer selection between competing upload paths.

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