Skip to main content
Glama

copy_file_from_project

Copy a file, such as an XSL transform, from one Workday Studio project into another to reuse an existing integration pattern as a starting point.

Instructions

Copy a file (typically an XSL transform) from one Studio project into another. The most common starting point when building a new integration based on an existing pattern.

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": {
      "source_project": "<source_project>",
      "source_file_path": "<source_file_path>",
      "target_project": "<target_project>"
    },
    "name": "copy_file_from_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_projectYesThe project to copy from
target_projectYesThe project to copy into
source_file_pathYesFile path relative to source project root (e.g. ws/WSAR-INF/GetWorkersWS.xsl)
target_file_pathNoDestination path relative to target project root. Defaults to the same relative path as the source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for what is implicitly a write operation into another project. It never states what happens if the target file already exists (overwrite, error, or version), whether missing target directories are created, or what the call returns on success. For a cross-project mutation with zero annotation coverage, this is a substantial gap.

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?

Two sentences with zero filler; the core action and direction are front-loaded in the first sentence and the usage hint follows immediately. Nothing is repeated from the schema or title.

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

Completeness2/5

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

With no annotations, no output schema, and four parameters, the definition should describe the mutation's side effects and failure modes. It leaves an agent unable to predict overwrite behavior, directory creation, or return value, which are exactly the facts a copy-across-projects tool needs.

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 description coverage is 100%, so all four parameters, including the defaulted target_file_path, are already documented in the schema. The description adds only the parenthetical that the source is typically an XSL transform, which slightly informs what source_file_path accepts but adds no path syntax or constraint beyond the schema.

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 names a specific verb and resource ('Copy a file') and a specific scope ('from one Studio project into another'), plus a typical file kind ('typically an XSL transform'). An agent can tell this apart from create_xsl_transform or write_integration_file, though it never explicitly names a sibling to contrast with.

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

Usage Guidelines3/5

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

'The most common starting point when building a new integration based on an existing pattern' gives a clear usage context, which is more than a bare purpose statement. However, there is no when-not guidance, no mention of prerequisites (do both projects need to exist?), and no alternative named for copying within the same project or moving rather than copying.

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