Skip to main content
Glama

Upload a file to Luw.ai

luw_upload_file

Upload an image, video, or 3D file to Luw.ai storage and receive a shareable URL for use across Luw.ai tools, including re-hosting or permanent storage.

Instructions

Upload an image, video or 3D file to Luw.ai storage and get a URL usable by every Luw.ai tool. Rarely needed: all tools already accept local paths and data: URIs and upload them automatically. Useful to get a shareable URL, to re-host an image from a site Luw.ai can't reach, or to store a file permanently.

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": {
      "source": "<source>"
    },
    "name": "luw_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesLocal file path, file:// URL, data: URI, or an https:// URL to copy into Luw.ai storage.
persistentNoKeep the file in your Luw.ai storage permanently. Default: temporary (not added to your library).
persona_idNoPersona to store a persistent file under (default: your first persona).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.18
    • changedInput schema / properties / persistent / description
      Previous value: -"Keep the file in your Luw.ai storage permanently. Default: temporary, auto-deleted after 12 hours."New value: +"Keep the file in your Luw.ai storage permanently. Default: temporary (not added to your library)."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the bar is lower; the description still adds that the file lands in Luw.ai storage and that the URL is consumable by every tool. It does not mention that repeat uploads of the same file create duplicate assets (relevant given idempotentHint=false) or any size/type limits. Overall solid added context beyond the annotations.

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?

Three sentences, front-loaded with the core action and its output, followed by the usage caveat and concrete cases. No filler or repetition; every clause carries either capability or routing information.

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 three-parameter write tool with no output schema, the description covers purpose, output (a URL), and when to skip it, which is nearly everything an agent needs. The remaining gap is operational detail such as duplicate handling and storage limits, which the schema and annotations do not supply either.

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 coverage is 100%, so the baseline is 3, but the description goes slightly beyond by tying use cases to source values: local paths and data: URIs are handled automatically, while an "image from a site Luw.ai can't reach" maps to the https:// copy mode. It still does not discuss the persistent/persona_id interaction, which remains schema-only.

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 ("Upload an image, video or 3D file to Luw.ai storage") and names the concrete outcome ("get a URL usable by every Luw.ai tool"). The accepted file classes and the returned artifact make it immediately distinguishable from the generation/editing siblings.

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?

Explicitly sets the default expectation with "Rarely needed: all tools already accept local paths and data: URIs and upload them automatically," which is an effective when-not rule. It then enumerates three precise when-to-use cases: shareable URL, re-hosting an unreachable image, and permanent storage.

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