Galatic.ai

Upload media

upload_media

Get a presigned URL to upload one file: then PUT the bytes to uploadUrl within 10 minutes with the same Content-Type (and exactly sizeBytes, when given). Returns { uploadUrl, publicUrl, presignedGetUrl, s3Key, assetId }; both GET URLs expire after one hour. type is required by the server (400 without it). Images, video, audio and documents are accepted, within the plan's size and storage limits (403/413). The upload does not appear in list_gallery: it is a file you can pass by URL or s3Key to tools such as edit_image or save_artist.

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": {
      "fileName": "<fileName>",
      "contentType": "<contentType>",
      "type": "<type>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "upload_media"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Required by the server; names the storage folder, e.g. "image" or "video".
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`fileName`	Yes
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`sizeBytes`	No	Exact file size; the PUT must match it.
`contentType`	Yes	MIME type, e.g. "image/png"; the PUT must send the same.
`durationSec`	No	For audio and video, checked against plan limits.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / required

Previous value: -[
-  "fileName",
-  "contentType",
-  "context",
-  "llm_model"
-]New value: +[
+  "fileName",
+  "contentType",
+  "type",
+  "context",
+  "llm_model"
+]

Changed4 schema fields changedOct 27, 2026

addedInput schema / properties / contentType / description

Added value: +"MIME type, e.g. \"image/png\"; the PUT must send the same."

addedInput schema / properties / durationSec / description

Added value: +"For audio and video, checked against plan limits."

addedInput schema / properties / sizeBytes / description

Added value: +"Exact file size; the PUT must match it."

addedInput schema / properties / type / description

Added value: +"Required by the server; names the storage folder, e.g. \"image\" or \"video\"."

First observedOct 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-destructive), the description discloses the 10-minute PUT window, one-hour GET URL expiry, required `type` with a 400 failure, plan size/storage limits surfacing as 403/413, and that uploads are invisible to list_gallery. That is substantial behavioural context the annotations do not carry.

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

Conciseness4/5

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

One front-loaded sentence covers the flow, then return shape, then error/limit conditions, then the sibling relationship. Dense but every sentence carries information; the return-field list is slightly long in prose form.

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

Completeness5/5

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

For an 8-parameter, no-output-schema tool, the description still names the return fields (uploadUrl, publicUrl, presignedGetUrl, s3Key, assetId) and their expiries, and covers failure modes and downstream usage. Nothing an agent needs to call it correctly is missing.

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 already 88%, but the description still adds real semantics: `type` is server-required (400 without it), `sizeBytes` must match exactly, and `contentType` must be reused on the PUT. It does not touch conversation_id or llm_model, though the schema covers those adequately.

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 opens with a specific verb and resource ('Get a presigned URL to upload one file') and then states the exact PUT mechanics. It distinguishes itself from siblings by naming list_gallery, edit_image and save_artist and explaining how the output relates to them.

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 states when to use it and how: put bytes to uploadUrl within 10 minutes with matching Content-Type and sizeBytes. It also contrasts against list_gallery and tells the agent what to do next (pass the URL or s3Key to edit_image or save_artist).

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

All Galatic.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.