Skip to main content
Glama
PurdueRCAC

Globus MCP Server

by PurdueRCAC

transfer

Submit an asynchronous file transfer task between Globus endpoints, with options for recursive directories, sync strategies, and checksum verification.

Instructions

Submit an asynchronous transfer task between Globus endpoints.

This submits a transfer task and returns immediately. The transfer runs server-side and can be monitored with task_show() or waited on with task_wait().

Args: source_endpoint: UUID of the source endpoint. source_path: Path to the file or directory on the source. dest_endpoint: UUID of the destination endpoint. dest_path: Path where data should be placed on destination. recursive: If True, transfer directories recursively. sync_level: Sync strategy for existing files: - None: Overwrite all files - 'exists': Skip if destination exists - 'size': Skip if same size - 'mtime': Skip if same size and modification time - 'checksum': Skip if same checksum label: Optional label for the transfer task. verify_checksum: If True, verify checksums after transfer. preserve_timestamp: If True, preserve modification times. encrypt_data: If True, encrypt data in transit.

Returns: Dict with 'task_id', 'submission_id', 'message', and other details. Use the 'task_id' with task_show() or task_wait().

Examples: # Transfer a single file result = transfer( source_endpoint="uuid1", source_path="/data/file.tar.gz", dest_endpoint="uuid2", dest_path="/scratch/file.tar.gz" ) task_id = result['task_id']

# Transfer a directory
transfer(
    source_endpoint="uuid1",
    source_path="/project/results/",
    dest_endpoint="uuid2",
    dest_path="/archive/results/",
    recursive=True,
    label="Archive project results"
)

# Sync with checksum verification
transfer(
    source_endpoint="uuid1",
    source_path="/data/",
    dest_endpoint="uuid2",
    dest_path="/backup/",
    recursive=True,
    sync_level="checksum",
    verify_checksum=True
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_endpointYes
source_pathYes
dest_endpointYes
dest_pathYes
recursiveNo
sync_levelNo
labelNo
verify_checksumNo
preserve_timestampNo
encrypt_dataNo

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 carries full burden. It discloses the async behavior and monitoring needed but lacks details on permissions, rate limits, or potential overwrite behavior (though sync_level implies it). Could be more transparent about prerequisites and what happens to destination files.

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 well-structured with sections for summary, args, returns, and examples. However, it is somewhat lengthy; the examples could be condensed or moved to reduce verbosity without losing clarity.

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 tool's complexity (10 parameters, required fields, async behavior), the description is fairly complete. It covers behavior, parameter details, return value, and usage examples. Minor gaps in behavioral transparency (permissions, error handling) prevent a perfect score.

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 the description provides thorough explanations for all 10 parameters, including sync_level options with valid values. Examples further clarify parameter usage, adding significant value 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?

The description clearly states it submits an asynchronous transfer task between Globus endpoints, specifying the verb and resource. It distinguishes from siblings like transfer_batch and compute_* 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 description explains the asynchronous nature and suggests using task_show() or task_wait() for monitoring. It provides examples but does not explicitly state when not to use this tool versus alternatives like transfer_batch.

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/PurdueRCAC/globus-mcp'

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