Skip to main content
Glama
kychee-com

run402-mcp

by kychee-com
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

assets_put

Upload files or inline content to project storage via direct-to-S3. Optionally set public/private visibility, enable immutable content-addressed URLs, and get responsive image variants.

Instructions

Upload a blob (file or inline content) to project storage via direct-to-S3. Accepts local_path (any size up to 5 TiB) or content (≤ 1 MB inline). Public blobs get a CDN URL; private blobs require authenticated reads. Use immutable: true to produce a content-addressed URL that never needs cache invalidation. For image uploads (jpeg/png/webp/heic/heif), the gateway also returns width_px/height_px/blurhash/display_url and a variants map (thumb 320w, medium 800w, large 1920w WebP — plus display_jpeg for HEIC sources) so apps can render responsive thumbnails without re-encoding client-side. See the SDK docs for the full AssetRef shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesDestination key (path in the project's blob namespace). No leading slash. Example: 'images/logo.png' or 'circuits/v1.zkey'.
contentNoInline content to upload (UTF-8 string). For small blobs ≤ 1 MB. Mutually exclusive with `local_path`.
metadataNov1.50: caller-provided flat metadata stored alongside the asset. Object with string / number / boolean / string[] leaves; ≤4 KB serialized. Nested objects rejected with INVALID_ASSET_METADATA (HTTP 400).
immutableNoWhen true, the returned URL includes a content-hash suffix so overwrites produce distinct URLs. CLI auto-computes sha256.
local_pathNoPath to a local file to upload. Mutually exclusive with `content`.
project_idYesProject ID
visibilityNoDefault: public. Public blobs get a CDN URL; private blobs require authenticated reads.
exif_policyNov1.50: EXIF retention policy for image uploads. Default 'keep'. 'strip' discards EXIF from the stored bytes and the image_exif response field.
content_typeNoMIME type (auto-detected from file extension if omitted).

Tool Definition Quality

A3.9/5.0
Behavior4/5

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

With no annotations, the description covers key behaviors: direct-to-S3, public/private visibility, immutable URLs, size limits (5 TiB vs 1 MB), image variant generation, EXIF policy, and auto-detected content type. However, it does not mention error cases or conflict behavior (e.g., overwrite vs. fail).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph with multiple details, not front-loaded. It is adequate but could be more concise and structured (e.g., using bullet points for image handling). Some redundancy with schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers many aspects (purpose, size, visibility, immutable, image processing) but omits the return shape (defers to SDK docs), error handling, and conflict semantics. For a complex mutation with 9 parameters, this is a notable gap.

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 100%, baseline 3. The description adds context beyond schema: size limits for local_path vs content, immutable URL semantics, image processing details, and EXIF policy explanation. This adds significant value.

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 clearly states 'Upload a blob (file or inline content) to project storage via direct-to-S3', specifying the verb and resource. It distinguishes from sibling tools like assets_get (download) and assets_ls (list).

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?

The description does not explicitly state when to use this tool versus alternatives. It provides details on behavior but lacks guidance on exclusions or context for choosing over other methods.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kychee-com/run402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server