Skip to main content
Glama

read_integration_file

Reads contents of a specific file in a Workday Studio project. Locate the correct file path with list_project_files first.

Instructions

Read the content of a specific file in a Studio project. Use list_project_files first to find the correct path.

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": "read_integration_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesPath to the file relative to the project root (e.g. ws/WSAR-INF/address-transform.xsl)
project_nameYesThe Studio project name (e.g. INT001_Sample_Integration)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. The verb "read" does establish that this is a non-mutating operation and the prerequisite sentence implies a path must be valid before calling, but nothing is said about what happens on a missing file, encoding, binary/large files, or what the call returns. For a simple read tool that is a moderate gap rather than a critical one.

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, zero filler, with the purpose front-loaded and the operational prerequisite second. Every clause earns its place.

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?

For a two-parameter, fully documented read tool with no output schema, the definition is adequate to invoke correctly but thin: it says nothing about failure modes or output shape, and with no annotations there is no other structured source for that information.

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%, and both parameters carry examples (project_name like INT001_Sample_Integration, file_path like ws/WSAR-INF/address-transform.xsl), so the schema already does the heavy lifting. The description adds only the framing that file_path is relative to a project root via the pointer to list_project_files, which is a marginal addition over structured data.

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?

"Read the content of a specific file in a Studio project" gives a concrete verb (read) and resource (file content) scoped to a project, which clearly separates it from write_integration_file and the listing tools. It stops short of explicitly naming the write sibling, but the read/write distinction is unmistakable.

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 supplies an explicit prerequisite workflow: "Use list_project_files first to find the correct path." That is real routing guidance for the common failure mode of guessing a path. There is no stated when-not condition (e.g. use search_studio_files for content search, or write_integration_file to modify), so it is clear but not exhaustive.

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