Skip to main content
Glama

SoFast

Upload files

upload_files

Stores files to be published, without changing any site. Omit upload_id to start a new upload; pass it to add files to the same one. Paths are relative to the site root, e.g. index.html or assets/app.css. Sending a path again replaces the earlier copy. Uploads expire after a day.

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": {
      "files": "<files>"
    },
    "name": "upload_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
upload_idNoThe upload to add to. Omit to start a new upload.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds genuinely useful behavior: re-sending a path overwrites the earlier copy and uploads expire after a day. It omits any mention of size or count limits, permission requirements, or that the call returns an upload_id for later chaining.

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?

Five short sentences, each carrying distinct information, with the scope constraint front-loaded and the upload_id mechanics immediately after. No restatement of the name or title.

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 two-parameter tool with no output schema, the description covers scope, path semantics, overwrite behavior, and TTL. The notable gap is that it implies an upload_id exists without stating the call returns one, which an agent needs to chain into a later publish step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 50% (the files array itself and the nested file object lack descriptions), the description compensates well: it explains omit-vs-pass for upload_id, gives path examples, and states the overwrite rule. It still doesn't clarify how base64 content interacts with path semantics or what happens if the array spans multiple encodings.

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?

"Stores files to be published, without changing any site" gives a specific verb (stores), resource (files), and a negative scope that separates it from publish_site. An agent immediately knows this is a staging step, not a deploy step.

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?

The description establishes the staging context clearly ('to be published, without changing any site') and explains the two modes via upload_id (new vs. append). It never names publish_site as the required follow-up, so the workflow handoff is left to inference.

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