Skip to main content
Glama

build_solution

Dry-run or compile X++ projects in the open Visual Studio solution to validate builds before applying changes, with configurable logging, timeout, and best-practice checks.

Instructions

Dry-run or compile the X++ projects of the solution open in 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_solution"
  }
}

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.3/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety profile is covered. The description adds real context the annotations do not: that it targets the currently open Visual Studio solution and that a dry-run mode exists as distinct from an actual compile. It omits what a compile produces or where output goes, what happens on failure, and whether a dry-run has side effects.

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 tight sentence, front-loaded with the action verb and scoped to the target resource, with no filler. It is arguably too terse for an 7-parameter tool, but nothing present 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?

For a 7-parameter build tool with 0% schema coverage, this description is thin: an agent cannot tell from the text what path/root should point at, how logLevel or timeoutMs affect behavior, or what bestPractices toggles. The presence of an output schema relieves it of describing return values, but the input-side gaps are substantial.

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 0% across 7 parameters, so the description must carry the load, and it only loosely gestures at one of them ('dry-run' implies the dryRun flag and 'compile' implies dryRun=false). The path, root, logLevel, timeoutMs, bestPractices, and configuration parameters receive no explanation at all, though 2 are enums and the defaults are visible in the schema.

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 pair (dry-run or compile) and a specific resource (the X++ projects of the solution open in Visual Studio), including the implicit scope restriction to the currently open solution. It does not name or distinguish itself from build_project, build_model, or artifact_build, so an agent must infer why it would pick this over those siblings.

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?

The phrase 'dry-run or compile' implies two usage modes and the implicit precondition of a solution being open in Visual Studio. However, there is no explicit when-to-use versus when-not, and no routing to build_project/build_model for project- or model-scoped builds, leaving the agent to infer the boundary.

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