Skip to main content
Glama

delete_file

Deletes a file from a Workday Studio project, creating a .bak backup by default and preventing removal of required assembly and project files.

Instructions

Delete a file from a Studio project. Creates a .bak backup before deleting by default. Cannot delete 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>",
      "file_path": "<file_path>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesFile path relative to project root (e.g. ws/WSAR-INF/OldTransform.xsl)
project_nameYesThe Studio project name
create_backupNoWrite a .bak copy before deleting. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description must carry the behavior itself, and it does disclose the key facts: a .bak backup is created by default, and specific protected files cannot be deleted. What is still missing is whether the deletion is reversible from that backup and what happens on failure. That remaining gap does not outweigh the useful disclosure of backup and protected files.

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?

Three short sentences: purpose first, then the default backup behavior, then the protected-file constraints. Every sentence carries a fact the caller needs, and no wording is wasted.

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 three-parameter destructive tool with no output schema and no annotations, the description covers what gets destroyed, the backup safeguard and the hard restrictions. What is missing is error behavior and any permission or project-state requirement, but an agent can call it correctly with what it has.

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?

The schema already documents all three parameters at full coverage, including that create_backup defaults to true. The description restates the backup default without adding format or syntax detail. It also adds nothing about file_path, which is covered by the schema at a baseline 3.

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 gives a specific verb and resource: 'Delete a file from a Studio project.' The 'file' scope is concrete enough to separate it from delete_assembly_step or delete_file-style siblings. It stops short of naming an alternative, but the resource itself is unambiguous.

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?

Usage is implied by the wording and by the exclusion list (assembly.xml, assembly-diagram.xml, .project, .classpath cannot be deleted), which is useful negative guidance. There is no explicit statement of when to choose this tool over rename_file, copy_file_from_project or delete_assembly_step, and no prerequisite such as closing the project or needing permissions.

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