Skip to main content
Glama

create_studio_project

Scaffolds a new empty Workday Studio integration project in the Eclipse workspace, generating the full directory structure and a blank assembly.xml ready to open in Studio.

Instructions

Scaffold a new empty Workday Studio integration project in the Eclipse workspace. Creates the full project directory structure (.project, .classpath, .settings/, ws/WSAR-INF/) with a blank assembly.xml ready to open in Studio.

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

Input Schema

NameRequiredDescriptionDefault
project_nameYesThe project name (e.g. INT145_My_New_Integration). Used as the Eclipse project name and integration system name.

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 carries the full burden, and it does disclose the material behavior: a write that creates a directory tree and stub config files. It does not say what happens if a project of that name already exists, whether the operation is reversible or how to undo it, or whether any workspace/permission constraints apply.

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, front-loaded with the action and then the concrete artifacts produced. No filler, no restatement of the tool name, and the payoff ("ready to open in Studio") closes it efficiently.

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 single-parameter scaffolding tool with no output schema, the description covers what is created and implicitly where, which is nearly all an agent needs. The remaining gap is the lack of any stated failure mode (duplicate project name) or confirmation of the return value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter with 100% schema description coverage (the schema already explains project_name and its dual role as Eclipse project name and integration system name), so the baseline is high. The description adds no naming syntax or validation rules beyond the schema, which is acceptable at this coverage level.

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 ("Scaffold a new empty Workday Studio integration project in the Eclipse workspace") and enumerates exactly what is produced (.project, .classpath, .settings/, ws/WSAR-INF/, blank assembly.xml). It is clearly distinguishable from transform-creation siblings such as create_xsl_transform by the "empty project" scope, though no sibling is named explicitly.

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 only implied: "ready to open in Studio" hints that this is the first step before adding transforms or assembly steps, but there is no explicit statement of when to use this versus create_xsl_transform/create_peci_transform or what to do next. No preconditions (e.g. project name must be unique) or exclusions are given.

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