Skip to main content
Glama

build_project

Compile an X++ .rnrproj in the open Visual Studio, or dry-run the build to validate changes before committing them.

Instructions

Dry-run or compile an X++ .rnrproj in the open Visual 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": {
      "path": "<path>"
    },
    "name": "build_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo
dryRunNo
logLevelNonormal
timeoutMsNo
bestPracticesNo
configurationNoDebug

Output Schema

NameRequiredDescriptionDefault
okYes
cwdNo
argsNo
kindNo
logsNo
errorNo
indexNo
dryRunNo
signalNo
stderrNo
stdoutNo
targetNo
commandNo
successNo
exitCodeNo
timedOutNo
artifactsNo
cancelledNo
durationMsNo
diagnosticsNo
stderrTruncatedNo
stdoutTruncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is largely covered, and the description adds a real prerequisite the annotations lack: a Visual Studio instance must be open with the project loaded. It does not disclose what a non-dry-run compile produces or overwrites, how long builds take relative to the 30s default timeout, or whether the session is blocked during compilation.

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 tight sentence with the action front-loaded and no filler. Nothing in it is redundant with the name or title.

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?

For a 7-parameter build tool with zero schema description coverage and a default-dry-run semantic that materially changes behavior, one sentence is far too thin. The presence of an output schema excuses explaining return values, but the mode semantics, timeout meaning, and best-practices flag remain unexplained.

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 description coverage is 0% across 7 parameters, so the description carries the full burden and does not meet it. Only dryRun is obliquely explained via 'Dry-run'; path, root, logLevel, timeoutMs, bestPractices, configuration, and the Debug/Release choice are left undocumented in both schema and description.

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 pair ('Dry-run or compile') and a specific resource ('an X++ .rnrproj in the open Visual Studio'), so an agent knows exactly what operation it performs. It does not differentiate from sibling build tools such as build_solution, build_model, or artifact_build, so an agent cannot tell from the text alone which build entry point applies to a .rnrproj.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of prerequisites beyond the implicit 'open Visual Studio', and no routing to alternatives for solution or model builds. The 'dry-run or compile' phrasing hints at two modes but never says when each is appropriate, even though dryRun defaults to true.

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