Skip to main content
Glama

artifact_build

Create or dry-run Dynamics 365 X++ artifact XML with labels, resources, and optional project membership; verify changes before writing files. Does not compile X++.

Instructions

Dry-run or create artifact XML and any label/resource payload, reconcile optional project membership; this does not compile X++.

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": {
      "type": "<type>",
      "name": "<name>",
      "package": "<package>",
      "model": "<model>"
    },
    "name": "artifact_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
rootNo
typeYes
modelYes
dryRunNo
contentNo
packageYes
projectPathNo
labelContentNo
solutionPathNo
projectExpectedSha256No
resourceContentBase64No
companionExpectedSha256No

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
actionNo
dryRunNo
impactNo
changesNo
artifactNo
previousIdNo
impactTruncatedNo
solutionValidatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds genuinely new context: dry-run is the default posture, label/resource payloads get written, and project membership may be reconciled as a side effect, plus the explicit non-compilation scope. It does not explain the expected-SHA256 concurrency guards or what happens on mismatch, which matters for a mutating writer.

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?

A single dense sentence with the action and the exclusion front-loaded and no filler. It reads slightly run-on because three distinct operations are packed into one clause, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema justifies omitting return-value detail, but for a 13-parameter mutating tool with zero schema descriptions, one sentence is not enough. An agent still cannot tell how the SHA256 guards, content, and root interact before invoking it.

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

Parameters2/5

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

Schema coverage is 0% across 13 parameters, so the description must carry the semantics. It loosely maps to dryRun, labelContent, resourceContentBase64, and projectPath/solutionPath, but says nothing about content, root, model, package, or the two expectedSha256 fields, leaving most of the surface undocumented.

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 uses specific verbs and resources: dry-run or create artifact XML plus label/resource payloads, and reconcile project membership. The closing clause 'this does not compile X++' distinguishes it from the build_* siblings, though it does not name them 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?

Saying 'dry-run or create' implies a safe preview is the default mode, and the compile exclusion is a partial when-not signal steering agents to build_model/build_project/build_solution. But there is no explicit guidance on when to choose this over artifact_update, artifact_design, or artifact_validate, nor any stated prerequisites.

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