Sandbox Agent

Overview Schema Source Related Servers Discussions Admin

export_files

Instructions

Registers files for download and cross-session import (no host copy).

Files become available via the API download endpoint and for import_files
in other sessions. Result includes download_url for each file (API must
be running).

Args:
    session_id: ID returned by create_session.
    files: List of objects with "source" (path in container).
        Example: [{"source": "report.pdf"}, {"source": "/workspace/data.csv"}]

Returns:
    JSON with per-file results (session_id, path, success, size, error,
    download_url). path is always absolute (e.g. /workspace/file.png).

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": {
      "session_id": "<session_id>",
      "files": "<files>"
    },
    "name": "export_files"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes
`files`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0May 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description discloses key behaviors: no host copy, API must be running, and per-file result details. Lacks auth or rate limit info.

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?

Concise with clear summary, args, returns. No unnecessary words.

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?

Covers purpose, args, and returns adequately. Could mention error handling but overall complete given moderate complexity.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description explains session_id and files with an example, adding significant meaning beyond raw 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?

The description clearly states the tool registers files for download and cross-session import, distinguishing it from siblings like import_files.

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?

It explains that files become available via download endpoint and for import_files in other sessions, but does not explicitly state when not to use this tool.

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

Deploy Server