Skip to main content
Glama

rename_file

Rename a file within a Workday Studio project by specifying old and new paths, while protecting reserved files like assembly.xml, assembly-diagram.xml, .project, and .classpath.

Instructions

Rename a file within a Studio project. Cannot rename assembly.xml, assembly-diagram.xml, .project, or .classpath.

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": {
      "project_name": "<project_name>",
      "old_path": "<old_path>",
      "new_path": "<new_path>"
    },
    "name": "rename_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_pathYesNew file path relative to project root (e.g. ws/WSAR-INF/NewName.xsl)
old_pathYesCurrent file path relative to project root (e.g. ws/WSAR-INF/OldName.xsl)
project_nameYesThe Studio project name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that certain reserved files cannot be renamed, but it omits key mutation behavior such as overwrite handling, permissions, failure modes, and side effects.

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 short sentences, with the core action front-loaded and the filename exclusions immediately following. There is no redundant wording or filler.

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?

The description covers the basic scope and one important restriction, and the fully documented schema handles the parameters. However, without annotations or an output schema, it leaves meaningful behavioral questions unanswered for a file-mutating operation.

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 the schema already fully documents project_name, old_path, and new_path with examples. The description adds no additional parameter meaning beyond that baseline.

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 states a specific verb and resource, 'Rename a file,' and scopes it to 'within a Studio project.' This clearly distinguishes it from siblings such as rename_steps or delete_file without ambiguity.

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?

It gives clear contextual usage plus explicit exclusions by naming files that cannot be renamed. It does not mention alternatives for restricted files or when another sibling should be used instead, which keeps it below a 5.

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