Skip to main content
Glama
heresun

OrbStack MCP Server

by heresun

orbstack_machine_push

Transfer files from macOS to Linux machines using OrbStack. Specify source path, optional destination, and target machine for file transfer operations.

Instructions

将文件从 macOS 推送到 Linux 机器。

Args: params: 包含源文件路径、可选的目标路径和机器名

Returns: str: 传输结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the orbstack_machine_push tool handler.
    async def orbstack_machine_push(params: MachineFileTransferInput) -> str:
        """将文件从 macOS 推送到 Linux 机器。
    
        Args:
            params: 包含源文件路径、可选的目标路径和机器名
    
        Returns:
            str: 传输结果
        """
        args = ["push"]
        if params.machine:
            args.extend(["-m", params.machine])
        args.append(params.source)
        if params.destination:
            args.append(params.destination)
    
        code, stdout, stderr = await _run_orb(args)
        if code != 0:
            return _format_error(stderr)
        return f"文件已推送: {params.source}" + (f" -> {params.destination}" if params.destination else "")
  • Registration of the orbstack_machine_push tool using the @mcp.tool decorator.
    @mcp.tool(
        name="orbstack_machine_push",
        annotations={
            "title": "推送文件到 Linux 机器",
            "readOnlyHint": False,
            "destructiveHint": False,
            "idempotentHint": False,
            "openWorldHint": False,
        },
    )
Behavior3/5

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

The description adds minimal behavioral context beyond annotations. Annotations already indicate this is not read-only, not open-world, not idempotent, and not destructive. The description adds that it transfers files between macOS and Linux machines, but doesn't provide additional behavioral details like whether it overwrites existing files, what permissions are required, or how it handles errors. With annotations covering the basic safety profile, this earns a baseline score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise with three sentences, but the structure could be improved. The first sentence clearly states the purpose, but the Args and Returns sections are overly brief and don't add meaningful information beyond what's obvious from the tool name. The description is front-loaded with the main purpose, but subsequent sentences don't earn their place with valuable additional context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this is a file transfer tool with 1 parameter (a nested object with 3 fields), 0% schema description coverage, and an output schema exists, the description is minimally adequate. It states what the tool does but lacks important context about how it works, what errors might occur, or what the '传输结果' (transfer result) output actually contains. The existence of an output schema helps, but the description should provide more operational context for a tool that modifies system state.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries full burden for parameter documentation. While the description mentions '包含源文件路径、可选的目标路径和机器名' (contains source file path, optional destination path, and machine name), this only lists parameter names without explaining their semantics, constraints, or relationships. It doesn't clarify what format paths should use, what 'machine name' refers to, or how defaults work when optional parameters are omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: '将文件从 macOS 推送到 Linux 机器' (push files from macOS to Linux machine). It specifies both the verb ('push') and resource ('files'), and distinguishes it from sibling tools like 'orbstack_machine_pull' which would move files in the opposite direction. However, it doesn't explicitly differentiate from other file-related tools like 'orbstack_docker_exec' or 'orbstack_machine_run' that might also handle files.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate compared to other file transfer methods or sibling tools like 'orbstack_machine_pull' for reverse transfers. The only implicit usage context is transferring files from macOS to Linux, but no explicit when/when-not guidance is provided.

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/heresun/orbstack-mcp'

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