Send Out

Prepare file transfer

prepare_transfer

Stores one text file behind a temporary download link and shows a transfer card. Use only when the user wants a hosted download link. To stage a file, send file_name and content (ttl_hours is optional, 1 to 168, default 24). To check a link made earlier, send only transfer_id. Returns download_url, file_name, sha256, size_bytes, expires_at and transfer_id; ChatGPT also shows a card with the file details, time left and a download button. With no content and no transfer_id it stages nothing and returns status ready. Do not use to show a draft: draft_email, create_calendar_event and create_markdown_file already return the file text. The file is stored until the link expires.

Input Schema

TableJSON Schema

Name	Required	Description
`file`	No	Set by ChatGPT when the user opens the card from a file. Do not fill this in yourself.
`content`	No	Full text of the file to stage (at most 200,000 characters). Send it together with file_name. Without content, nothing is stored.
`file_name`	No	File name with its extension, such as "report.md", "invite.ics" or "draft.eml". Send it together with content to stage a file.
`mime_type`	No	Optional MIME type, such as "text/markdown", "text/calendar" or "message/rfc822". Guessed from file_name when omitted.
`ttl_hours`	No	Hours until the download link expires, from 1 to 168. Default 24.
`transfer_id`	No	ID of a transfer made earlier, from its transfer_id field (32 hex characters). Send it alone to check that link. An unknown or expired ID returns transfer_not_found.

Output Schema

TableJSON Schema

Name	Required	Description
`file`	No	The file ChatGPT passed when the card was opened from a file. Set only in that case.
`notes`	No	Short notes to pass on to the user. Set when status is ok.
`sha256`	No	SHA-256 checksum of the file as 64 hex characters. Set when status is ok.
`status`	Yes	ok: a file is staged or found, and the download fields are set. ready: nothing is staged yet; read message for what to send.
`message`	No	Set when status is ready: says what to send next.
`file_name`	No	Cleaned file name. Set when status is ok, and when ready if a name was given.
`mime_type`	No	MIME type of the file. Set when status is ok.
`expires_at`	No	When the link stops working, as an ISO 8601 UTC time. Set when status is ok.
`size_bytes`	No	File size in bytes. Set when status is ok.
`transfer_id`	No	ID to check this link again later. Set when status is ok.
`download_url`	No	Direct download URL. Set when status is ok.
`interactive_ui`	Yes	Resource URI of the transfer card.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "content": "# Weekly report\n- Shipped on time",
-    "file_name": "report.md",
-    "ttl_hours": 1
-  }
-]

Changed1 schema field changedOct 15, 2026

addedInput schema / examples

Added value: +[
+  {
+    "content": "# Weekly report\n- Shipped on time",
+    "file_name": "report.md",
+    "ttl_hours": 1
+  }
+]

Changed19 schema fields changedOct 11, 2026

changedInput schema / properties / content / description

Previous value: -"Text or document content of the file to transfer."New value: +"Full text of the file to stage (at most 200,000 characters). Send it together with file_name. Without content, nothing is stored."

changedInput schema / properties / file / description

Previous value: -"File metadata injected when opened through a file extension entrypoint in ChatGPT."New value: +"Set by ChatGPT when the user opens the card from a file. Do not fill this in yourself."

changedInput schema / properties / file_name / description

Previous value: -"Name of the file to transfer (e.g. report.md, invite.ics, draft.eml)."New value: +"File name with its extension, such as \"report.md\", \"invite.ics\" or \"draft.eml\". Send it together with content to stage a file."

changedInput schema / properties / mime_type / description

Previous value: -"Optional MIME type (e.g. text/markdown, text/calendar, message/rfc822). Inferred from file_name if omitted."New value: +"Optional MIME type, such as \"text/markdown\", \"text/calendar\" or \"message/rfc822\". Guessed from file_name when omitted."

changedInput schema / properties / transfer_id / description

Previous value: -"Optional existing transfer ID to inspect."New value: +"ID of a transfer made earlier, from its transfer_id field (32 hex characters). Send it alone to check that link. An unknown or expired ID returns transfer_not_found."

changedInput schema / properties / ttl_hours / description

Previous value: -"Hours until the download link expires (1-168 hours; default is 24)."New value: +"Hours until the download link expires, from 1 to 168. Default 24."

changedOutput schema / properties / download_url / description

Previous value: -"Direct download URL for the file."New value: +"Direct download URL. Set when status is ok."

changedOutput schema / properties / expires_at / description

Previous value: -"ISO 8601 expiration timestamp."New value: +"When the link stops working, as an ISO 8601 UTC time. Set when status is ok."

addedOutput schema / properties / file / description

Added value: +"The file ChatGPT passed when the card was opened from a file. Set only in that case."

addedOutput schema / properties / file / properties

Added value: +{
+  "name": {
+    "type": "string"
+  },
+  "resourceUri": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / file_name / description

Previous value: -"Sanitized name of the file."New value: +"Cleaned file name. Set when status is ok, and when ready if a name was given."

changedOutput schema / properties / interactive_ui / description

Previous value: -"Resource URI of the interactive transfer card."New value: +"Resource URI of the transfer card."

addedOutput schema / properties / message / description

Added value: +"Set when status is ready: says what to send next."

changedOutput schema / properties / mime_type / description

Previous value: -"MIME content type."New value: +"MIME type of the file. Set when status is ok."

addedOutput schema / properties / notes / description

Added value: +"Short notes to pass on to the user. Set when status is ok."

changedOutput schema / properties / sha256 / description

Previous value: -"Hex-encoded SHA-256 integrity checksum."New value: +"SHA-256 checksum of the file as 64 hex characters. Set when status is ok."

changedOutput schema / properties / size_bytes / description

Previous value: -"Total size in bytes."New value: +"File size in bytes. Set when status is ok."

addedOutput schema / properties / status / description

Added value: +"ok: a file is staged or found, and the download fields are set. ready: nothing is staged yet; read message for what to send."

addedOutput schema / properties / transfer_id / description

Added value: +"ID to check this link again later. Set when status is ok."

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say the call writes, is not idempotent and is not destructive. The description adds the details that matter: files persist until the link expires, an empty call stages nothing and returns status ready, and an unknown or expired ID yields transfer_not_found. It also describes the card the user sees, something no annotation could convey.

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?

The main constraint comes first, followed by the two modes and then the exclusion. It is a little long, and listing the return fields duplicates the output schema, so a few words could be cut without losing meaning.

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?

Covers both operating modes, the limits on content and TTL, how long the file lives, the error case and what the user sees. An output schema exists, so the extra return-value sentence is harmless; nothing needed to call this 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 100%, so the baseline is 3. The description rises above that by explaining how parameters combine: file_name plus content to stage, transfer_id alone to check, and neither to get a ready status. It repeats the ttl_hours range and default that the schema already documents.

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 action (stores one text file behind a temporary download link) and its visible side effect (shows a transfer card). This clearly distinguishes it from file-creating siblings that only return text.

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 says 'Use only when the user wants a hosted download link' and names concrete alternatives (draft_email, create_calendar_event, create_markdown_file) with the reason to prefer them. It also separates the two operational modes: stage versus check.

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

All Send Out 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.