Skip to main content
Glama

import_files

Import files into an isolated sandbox session from your host or from another session using source paths or session references.

Instructions

Imports files into the sandbox from host or from another session.

Each entry can be:
- Host path: "source" (host path), optional "destination"
- Cross-session: "session_id" (source session), "path" (container path),
  optional "destination" — file must have been exported from that session.

Args:
    session_id: ID returned by create_session (destination).
    files: List of file objects. Examples:
        [{"source": "/tmp/report.pdf", "destination": "report.pdf"}]
        [{"session_id": "abc123", "path": "/workspace/out.csv", "destination": "out.csv"}]

Returns:
    JSON with per-file results (source, destination, success, size, error).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
filesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It describes the import process and return format but lacks details on permissions, overwrite behavior, or size limits. It is honest but not exhaustive.

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 description is structured with sections and examples, though it is somewhat verbose. The return type is mentioned but redundant given the output schema. Overall, it is clear and efficiently organized.

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?

Given the presence of an output schema and sibling tools, the description covers input formats, examples, and return value. It is mostly complete but could mention when to use this tool versus export_files or other alternatives.

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?

With 0% schema coverage, the description compensates well by explaining that session_id is the destination session and files is a list of objects with specific structures and examples, adding significant meaning beyond the bare 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 it imports files into the sandbox and distinguishes between host path and cross-session imports, specifying the required fields for each. This provides a specific verb and resource, differentiating from siblings like export_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?

The description explains when to use each entry format (host path vs cross-session) and notes that cross-session files must have been previously exported. However, it does not explicitly state when not to use this tool or compare directly with sibling tools like create_session or export_files.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eduresser/sandbox-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server