Skip to main content
Glama

build_model

Dry-run or compile a Dynamics 365 model in the open Visual Studio with bounded logs and configurable build options.

Instructions

Dry-run or compile a Dynamics 365 model in the open Visual Studio (Dynamics 365 > Build Models) and bounded logs.

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

Input Schema

NameRequiredDescriptionDefault
modelYes
dryRunNo
optionsNoDynamics 365 Build Models dialog options. synchronizeDatabase needs policies.allowDatabaseSynchronization and deployToOnlineEnvironment needs policies.allowEndpointMutations.
packageYes
logLevelNonormal
timeoutMsNo
bestPracticesNo

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

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

Annotations already declare the write-but-non-destructive profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's main added value is that a Visual Studio instance must be open. It omits what gets written, whether an online deploy can occur, timeout behavior, and what 'bounded logs' means, which are the traits beyond annotations an agent would want.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The verb and resource are front-loaded in a single sentence, which is good, but the trailing clause 'and bounded logs' is vague and reads as a truncated thought rather than a useful qualifier.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. However, for a 7-parameter tool with a nested options object, defaulting dryRun to true and having several gated option flags, the description is thin on the operational context an agent needs to call it correctly.

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 only 14% across 7 parameters including a nested options object, yet the description adds nothing about package, model, bestPractices, logLevel, or timeoutMs. The policy notes for synchronizeDatabase and deployToOnlineEnvironment live in the schema, not here, so the description fails to compensate for the coverage gap.

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 ('a Dynamics 365 model in the open Visual Studio'), with a UI anchor ('Dynamics 365 > Build Models'). It does not contrast itself with siblings like build_project or build_solution, but the 'model' resource is distinctive enough to separate it.

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 'dry-run or compile' phrasing implies the two modes and matches the dryRun flag, but there is no explicit guidance on when to use this over build_project/build_solution, no stated prerequisites beyond an open Visual Studio, and no exclusions.

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