Skip to main content
Glama

Handoff: Send Files to Users & Agents

by io.github.jueluddinsf
OverviewDiscussionsAdmin

Save a file

save_file

Save a private file for this account. Pass name and content_text or content_base64. Returns the file id and metadata. Does not share the file. Requires your API key.

Input Schema

NameRequiredDescriptionDefault
mimeNoMIME type. Inferred from the file name when omitted.
nameYesFile name with an extension. No slashes or control characters.
api_keyNoSecret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you share.
content_textNoUTF-8 text. Pass exactly one of content_text or content_base64.
content_base64NoStandard or url-safe base64. A data:*;base64, prefix is stripped. Example: aGk=

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / content_base64 / description
      Previous value: -"Standard base64 file bytes. Do not include a data: URL prefix."New value: +"Standard or url-safe base64. A data:*;base64, prefix is stripped. Example: aGk="
  2. Changed4 schema fields changed
    • addedInput schema / properties / content_text
      Added value: +{
+  "description": "UTF-8 text. Pass exactly one of content_text or content_base64.",
+  "maxLength": 70000000,
+  "type": "string"
+}
    • removedInput schema / properties / mime / default
      Removed value: -"application/octet-stream"
    • changedInput schema / properties / mime / description
      Previous value: -"MIME type, for example text/plain or application/pdf."New value: +"MIME type. Inferred from the file name when omitted."
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "content_base64"
-]New value: +[
+  "name"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds value beyond annotations by disclosing the return shape ('file id and metadata'), the auth requirement, and the privacy guarantee (not shared). It omits the notable fact that no idempotency exists — repeated saves with the same name likely create new files — which the annotations flag but never explain.

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?

Four short sentences, front-loaded with purpose, then inputs, return, sharing behavior, and auth. No 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?

With no output schema, the description correctly supplies the return value (file id and metadata) and auth needs. Minor gaps remain around size limits and non-idempotent duplicate behavior, but nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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. The description only restates the schema's own rule that exactly one of content_text or content_base64 is used and lists the required name; it adds no format or sizing detail beyond the schema.

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 ('Save a private file for this account') plus the key scope constraint ('Does not share the file'), which cleanly separates it from the sibling share_file/create_share_link tools.

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

Usage Guidelines4/5

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

The 'Does not share the file' clause implicitly routes agents to share_file when sharing is wanted, and 'Requires your API key' signals a precondition. It stops short of explicitly naming when to pick a sibling instead.

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

All Handoff: Send Files to Users & Agents toolsInspect
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.

Resources