Skip to main content
Glama

run_systest_class

Run D365FO unit test classes with SysTestConsole to get per-method results, or target a single test method for focused validation.

Instructions

Run D365FO unit test classes (SysTestConsole; UDE: cloud runtime), with per-method results.

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": {
      "className": "<className>"
    },
    "name": "run_systest_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
classNameYesSysTest class, e.g. "MyModuleTest". UDE: several of one model, comma-separated, in one run
modelNameNoThe model containing the test class. Auto-detected if omitted.
testMethodNoOptional: run only this specific test method within the class (e.g. "testValidation").
packagePathNoPackagesLocalDirectory root path. Auto-detected if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.0
    • changedInput schema / properties / className / description
      Previous value: -"The name of the SysTest class to run (e.g. \"MyModuleTest\")"New value: +"SysTest class, e.g. \"MyModuleTest\". UDE: several of one model, comma-separated, in one run"
  2. Changed2 schema fields changedv1.14.0
    • changedInput schema / properties / modelName / description
      Previous value: -"The model containing the test class. Auto-detected from .mcp.json if omitted."New value: +"The model containing the test class. Auto-detected if omitted."
    • changedInput schema / properties / packagePath / description
      Previous value: -"PackagesLocalDirectory root path. Auto-detected from .mcp.json if omitted."New value: +"PackagesLocalDirectory root path. Auto-detected if omitted."
  3. First observedv1.8.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, and the description adds real context beyond them: the execution engine (SysTestConsole), the runtime mode (UDE/cloud), and that results are reported per method rather than as one aggregate. It still omits behavior an agent would want before invoking — expected duration, whether a deployed/test environment is required, and what happens when tests fail (error vs. result payload).

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?

A single sentence with the core action front-loaded and each clause contributing new information (engine, runtime, result granularity); nothing is redundant or padded.

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?

With a fully described four-parameter schema and no output schema, most of the burden is already carried by structured data, and the description correctly notes the per-method result shape. However, for a test-execution tool that can be slow and environment-dependent, the absence of prerequisite or duration context leaves a meaningful gap for correct invocation sequencing.

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 all four parameters (className, modelName, testMethod, packagePath) are already documented with examples and auto-detection notes. The description adds no syntax or format detail beyond the schema; per the rubric, full coverage sets the baseline at 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 names a specific verb and resource ('Run D365FO unit test classes'), names the underlying runner (SysTestConsole) and the cloud/UDE runtime variant, and states the result shape ('per-method results'). It is clearly not a build, analysis, or best-practice check tool, so an agent can separate it from siblings like run_bp_check or build_d365fo_project without opening the schema, though it never names an explicit alternative.

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: the parenthetical '(UDE: cloud runtime)' hints this is the path for cloud-hosted UDE environments, but there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g. whether the project must be built or symbols indexed first, which siblings like build_d365fo_project or update_symbol_index would cover).

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