Skip to main content
Glama

list_project_files

Lists integration files in a Workday Studio project, focusing on ws/WSAR-INF transforms and assembly files, with optional filtering by XSL, XML, or all file types.

Instructions

List all integration files in a specific Studio project. Focuses on ws/WSAR-INF/ where transforms and assembly files live.

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>"
    },
    "name": "list_project_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_typeNoFilter by file type: "xsl" for transforms, "xml" for XML/assembly files, "all" for all integration files. Defaults to "all".
project_nameYesThe name of the Studio integration project (e.g. INT001_Sample_Integration)

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 must carry the full behavioral burden. It doesn't state whether the listing is recursive, whether missing projects error or return empty, what the output entries contain (paths? names? metadata?), or any pagination or permission constraints.

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

Conciseness4/5

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

Two short, front-loaded sentences with no filler. The second sentence adds the scope detail but could have been merged or made explicit about recursion to earn full marks.

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?

It's a simple two-parameter read tool with a fully documented schema and no output schema, so little is needed. Still, without annotations or return-shape detail, an agent cannot predict the result format or whether the listing is recursive.

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% and the enum values are fully documented in the schema itself. The description adds only the folder scope (ws/WSAR-INF/), which is not a parameter but does clarify what project_name resolves to; baseline 3 applies.

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?

States a specific verb and resource (list all integration files in a Studio project) and narrows scope to ws/WSAR-INF/ where transforms and assembly files live. It does not explicitly distinguish itself from sibling search_studio_files or read_integration_file, so it stops short of a 5.

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 description implies when to use it (browsing the contents of a project's integration directory) but gives no explicit when-not guidance or named alternatives such as search_studio_files for cross-project search or read_integration_file for reading contents.

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