Skip to main content
Glama
sandraschi

Windows Operations MCP

by sandraschi

winops_container_cp

Copy files between a Windows host and a Docker container by specifying source and destination paths with host: or container: prefixes. Direction is set by the source prefix, enabling outbound file retrieval or inbound file placement.

Instructions

Copy files between the host and a Docker container.

Direction is determined by the source prefix:

  • source="container:/tmp/data.json", destination="host:./out/" copies FROM container TO host

  • source="host:./script.py", destination="container:/tmp/" copies FROM host TO container

Return Format

{"success": bool, "source": str, "destination": str}

Examples

cp(container="app", source="host:./script.py", destination="container:/tmp/")
cp(container="db", source="container:/tmp/result.csv", destination="host:./output/")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesSource path. Format: 'host:/path/file' or 'container:/path/file' (prefix determines direction).
containerYesContainer name or ID.
destinationYesDestination path. Format: 'host:/path/' or 'container:/path/'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations are present but mostly default-false; the description adds the source-prefix direction rule and return format. However, it does not disclose overwrite behavior, dependency on a running container, or permissions, leaving some behavioral ambiguity.

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?

The description is front-loaded with the core purpose, then provides a concise direction table, return format, and two examples. Every section earns its place and there is 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?

For a simple three-parameter copy tool, the description covers the main semantics, direction behavior, and return value, especially with output schema present. Minor gaps around error/overwrite behavior prevent a 5.

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 schema already documents the prefix formats and required fields. The description's examples reinforce usage but do not add substantial new parameter semantics 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 opens with a specific verb and resource: 'Copy files between the host and a Docker container.' It clearly distinguishes this from sibling tools like winops_container_exec by focusing on file transfer with an explicit direction model.

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 two possible direction patterns with concrete examples, making when to use the tool clear. It does not explicitly name alternatives or exclusions, but the copy-vs-execute distinction is implicit from the sibling context.

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/sandraschi/windows-operations-mcp'

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