Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Upload Files

upload_asset

Creates an Asset Hub asset from local files by returning per-file upload links to PUT bytes to, then finishing the upload. Use it when a user asks to upload files to Meshive.

Instructions

Start uploading files from the user's computer as a new Asset Hub asset, when the user asks to upload them. This server can't read local files: it returns an upload link per file, you PUT each file's exact bytes to its link from your own shell, then call finish_upload. files = [{"path": name inside the asset (a file name, or a/b.txt for a folder), "size_bytes": exact size, "sha256": optional}]. One call makes one asset; name defaults from the files and asset_type (dataset, model, adapter, checkpoint, config, file) is guessed when omitted. Upload each with curl -fsS -T <local file> "<url>" (on Windows curl.exe, not PowerShell's curl alias). The links expire after presign_expires_in seconds and let anyone who has them upload into this asset: use them only in that command, never in files or other tools. Files over 200 MiB need the CLI instead (meshive asset-upload <path>, which uploads in parts); this tool then cancels and says so. Managed storage is billed per GiB-month (see the assets tool); accounts with no payment yet have a storage limit. The server keeps no operation record of this call, so operation_status can't look it up and a repeated call runs again.

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_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
filesYes
workspaceNo
asset_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses non-obvious behavior: links expire after presign_expires_in seconds, links are bearer-capable so must never be written into files or passed to other tools, large files fail and cancel, storage is billed per GiB-month with limits for unpaid accounts, and no operation record means operation_status cannot find the call. The 'repeated call runs again' statement corroborates idempotentHint=false rather than contradicting it.

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?

The operative instruction is front-loaded in the first two sentences, then details are grouped by concern (payload shape, upload command, security, limits, statelessness). Lines are dense but each carries a distinct operational fact; nothing reads as filler.

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 multi-step, out-of-band upload tool with an output schema present, it covers the mechanics, the safety constraint, the size ceiling, billing exposure, and lookup behavior. The main residual gap is that the workspace parameter and default-naming precedence for name are never explained.

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?

Schema description coverage is 0%, so the description must carry the parameters, and it does for the required one: it defines the files array element shape (path semantics including 'a/b.txt for a folder', exact size_bytes, optional sha256) and enumerates asset_type values the schema does not constrain. It leaves workspace and name's formatting largely unexplained, which keeps it off a 5.

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 ('Start uploading files from the user's computer as a new Asset Hub asset') and immediately frames the two-phase flow with its sibling finish_upload. An agent can distinguish this initiation step from the completion step without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('when the user asks to upload them'), an explicit hand-off ('call finish_upload'), and an explicit exclusion with an alternative for files over 200 MiB ('need the CLI instead ... this tool then cancels and says so'). That is when-to-use, when-not, and the substitute in one place.

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