Skip to main content
Glama

build_d365fo_project

Idempotent

Compiles an entire Dynamics 365 Finance and Operations model with xppc in one blocking call, fixing stale-symbol errors and optionally syncing the database.

Instructions

Build a D365FO model with xppc.exe (compiles the ENTIRE model, not one project). Blocks until done — call ONCE per build, do NOT poll (wait:false = legacy polling mode). fullBuild:true fixes "not been successfully compiled since it was last changed" stale-symbol errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build_d365fo_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoDefault true: one call returns the final result. false = legacy fire-and-forget.
forceNoKill any running build processes for this model and restart.
aosUrlNorestartAos root. Default: Infrastructure.HostUrl in AosService web.config; required on UDE.
dbSyncNoOn a SUCCESSFUL build, also run the database sync (SyncEngine.exe) — REQUIRED after any table/view/data-entity change. true = partial sync of the syncable objects in the project, full-model when it has none; an ARRAY syncs exactly those tables/views (much faster). With deploy: full sync in the environment.
deployNoUDE: on a SUCCESSFUL build, deploy the model's package to the cloud runtime that run_systest_class tests run in. dbSync unset: syncs only if schema changed (~20 min, else ~3).
bpCheckNoOn a SUCCESSFUL build, also run the best-practice checker and append its findings. Prefer this to a follow-up run_bp_check call: one build call instead of two round trips.
fullBuildNoFull recompile of TARGET model (not deps). Fixes stale symbols; auto when a table, EDT, enum or OData entity changes.
modelNameNoD365FO model name to build (e.g. MyCustomModel). Auto-detected from workspace if omitted.
restartAosNoAfter a successful build (+dbSync), restart the local IIS/IIS Express AOS serving aosUrl.
waitTimeoutMsNoMax ms to block (default 30 min) before a "still running" snapshot; the build continues.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.0
    • changedInput schema / properties / deploy / description
      Previous value: -"UDE: on a SUCCESSFUL build, deploy the model's package to the cloud runtime that run_systest_class tests run in. No DB sync (~3 min) unless dbSync (~20 min)."New value: +"UDE: on a SUCCESSFUL build, deploy the model's package to the cloud runtime that run_systest_class tests run in. dbSync unset: syncs only if schema changed (~20 min, else ~3)."
  2. Changed5 schema fields changedv1.24.0
    • changedInput schema / properties / dbSync / description
      Previous value: -"On a SUCCESSFUL build, also run the database sync (SyncEngine.exe) — REQUIRED after any table/view/data-entity change. true = partial sync of the syncable objects in the project, full-model when it has none; an ARRAY syncs exactly those tables/views (much faster)."New value: +"On a SUCCESSFUL build, also run the database sync (SyncEngine.exe) — REQUIRED after any table/view/data-entity change. true = partial sync of the syncable objects in the project, full-model when it has none; an ARRAY syncs exactly those tables/views (much faster). With deploy: full sync in the environment."
    • addedInput schema / properties / deploy
      Added value: +{
      +  "description": "UDE: on a SUCCESSFUL build, deploy the model's package to the cloud runtime that run_systest_class tests run in. No DB sync (~3 min) unless dbSync (~20 min).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / fullBuild / description
      Previous value: -"Full recompile of TARGET model (not deps). Fixes stale symbols; auto when an entity with OData actions changes."New value: +"Full recompile of TARGET model (not deps). Fixes stale symbols; auto when a table, EDT, enum or OData entity changes."
    • changedInput schema / properties / wait / description
      Previous value: -"When true (default) the tool blocks until the build finishes and returns the final result in a single call. The agent should make exactly one call per requested build. Set false for legacy fire-and-forget polling behaviour."New value: +"Default true: one call returns the final result. false = legacy fire-and-forget."
    • changedInput schema / properties / waitTimeoutMs / description
      Previous value: -"Maximum time (ms) to block when wait:true before returning a \"still running\" snapshot. Defaults to 30 minutes. The build itself continues in the background."New value: +"Max ms to block (default 30 min) before a \"still running\" snapshot; the build continues."
  3. Changed1 schema field changedv1.22.0
    • changedInput schema / properties / fullBuild / description
      Previous value: -"Full recompile of the TARGET model only; deps are not built. Use when xppc reports stale symbol errors."New value: +"Full recompile of TARGET model (not deps). Fixes stale symbols; auto when an entity with OData actions changes."
  4. Changed1 schema field changedv1.21.0
    • changedInput schema / properties / fullBuild / description
      Previous value: -"Full recompile of the TARGET model only (deps stay incremental). Use when xppc reports stale symbol errors."New value: +"Full recompile of the TARGET model only; deps are not built. Use when xppc reports stale symbol errors."
  5. Changed2 schema fields changedv1.19.1
    • addedInput schema / properties / aosUrl
      Added value: +{
      +  "description": "restartAos root. Default: Infrastructure.HostUrl in AosService web.config; required on UDE.",
      +  "type": "string"
      +}
    • addedInput schema / properties / restartAos
      Added value: +{
      +  "description": "After a successful build (+dbSync), restart the local IIS/IIS Express AOS serving aosUrl.",
      +  "type": "boolean"
      +}
  6. Changed3 schema fields changedv1.16.2
    • changedInput schema / properties / bpCheck / description
      Previous value: -"On a SUCCESSFUL build, also run the best-practice checker and append its findings — saves the usual follow-up run_bp_check call."New value: +"On a SUCCESSFUL build, also run the best-practice checker and append its findings. Prefer this to a follow-up run_bp_check call: one build call instead of two round trips."
    • addedInput schema / properties / dbSync
      Added value: +{
      +  "description": "On a SUCCESSFUL build, also run the database sync (SyncEngine.exe) — REQUIRED after any table/view/data-entity change. true = partial sync of the syncable objects in the project, full-model when it has none; an ARRAY syncs exactly those tables/views (much faster).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "boolean",
      +    "array"
      +  ]
      +}
    • removedInput schema / properties / projectPath
      Removed value: -{
      -  "description": "(Legacy) Absolute path to a .rnrproj file — used only to extract the model name when modelName is not provided.",
      -  "type": "string"
      -}
  7. Changed2 schema fields changedv1.14.0
    • addedInput schema / properties / bpCheck
      Added value: +{
      +  "description": "On a SUCCESSFUL build, also run the best-practice checker and append its findings — saves the usual follow-up run_bp_check call.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / buildReferencedModels
      Removed value: -{
      -  "description": "DISABLED — always ignored. Rebuilding dependency models on every build slows the run down and referenced models are expected to already be compiled.",
      -  "type": "boolean"
      -}
  8. Changed1 schema field changedv1.9.0
    • changedInput schema / properties / buildReferencedModels / description
      Previous value: -"Also build all custom/ISV models this model depends on before building the target. Skips Microsoft standard models."New value: +"DISABLED — always ignored. Rebuilding dependency models on every build slows the run down and referenced models are expected to already be compiled."
  9. First observedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare idempotentHint and destructiveHint=false, so the description carries real weight here: it discloses that the call blocks until completion and that a timeout returns a 'still running' snapshot rather than aborting. It does not mention the disruptive side effects (killing build processes, AOS restart) that follow from the schema's force/restartAos parameters.

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?

Three dense sentences with no filler: scope first, invocation protocol second, then the specific failure mode fullBuild solves. Front-loaded and every clause conveys an operational fact.

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

Completeness4/5

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

For a 10-parameter build tool with no output schema, the description covers scope, blocking behavior, and the highest-risk parameter (fullBuild). Remaining gaps — prerequisites like xppc.exe/AOS availability and what the result object contains — are partly covered by the 100%-documented schema, but not fully replaced.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by mapping fullBuild to the exact stale-symbol error text ('not been successfully compiled since it was last changed') and clarifying that wait controls blocking versus legacy polling. That adds diagnostic meaning an agent cannot get from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Build a D365FO model with xppc.exe') and immediately disambiguates scope: 'compiles the ENTIRE model, not one project.' That distinction separates it from sibling tools like verify_d365fo_project or run_bp_check without needing to read the schema.

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

Usage Guidelines4/5

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

Gives explicit invocation protocol — 'call ONCE per build, do NOT poll' — plus a pointer to the legacy path ('wait:false = legacy polling mode') and a trigger condition for fullBuild (stale-symbol errors). It stops short of naming when NOT to build or which sibling to use for verification-only needs.

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