Skip to main content
Glama

build_d365fo_project

Idempotent

Compile a Dynamics 365 Finance and Operations model with xppc.exe, blocking until the build completes. Use fullBuild to resolve stale symbol errors.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoWhen 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.
forceNoKill any running build processes for this model and restart.
fullBuildNoFull recompile of the TARGET model only (deps stay incremental). Use when xppc reports stale symbol errors.
modelNameNoD365FO model name to build (e.g. MyCustomModel). Auto-detected from workspace if omitted.
projectPathNo(Legacy) Absolute path to a .rnrproj file — used only to extract the model name when modelName is not provided.
waitTimeoutMsNoMaximum time (ms) to block when wait:true before returning a "still running" snapshot. Defaults to 30 minutes. The build itself continues in the background.
buildReferencedModelsNoDISABLED — always ignored. Rebuilding dependency models on every build slows the run down and referenced models are expected to already be compiled.
Behavior5/5

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

Beyond annotations, the description discloses critical behavioral traits: the tool blocks until done, wait:false is legacy polling, and fullBuild affects dependency handling. This adds meaningful context about execution behavior and error remediation.

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?

The description is two sentences, densely packed with key facts, and front-loaded. Every sentence provides actionable information without redundancy.

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 tool with no output schema, the description covers the main behavioral expectations (blocking, single call, fullBuild usage). It could mention return value format in more detail, but it does state that wait:true returns the final result, making it sufficiently complete.

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 baseline is 3. The description adds extra meaning beyond the schema by explaining wait:false legacy mode and fullBuild's role in fixing stale-symbol errors, which are not fully captured in the parameter descriptions.

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?

The description clearly states the tool builds a D365FO model using xppc.exe, with a specific verb and resource. It also distinguishes itself from project-level builds by emphasizing it compiles the entire model, differentiating it from sibling tools.

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?

The description gives explicit usage instructions: call once per build, do not poll, and use fullBuild for stale-symbol errors. It does not explicitly mention alternatives or when not to use the tool, but provides strong operational context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dynamics365ninja/d365fo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server