Skip to main content
Glama
dynamics365ninja

D365 F&O MCP Server

by dynamics365ninja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_workspace_info

Read-only

Retrieve the active workspace configuration at session start: model name, paths, environment type, and extension prefix. Flags missing prefixes so development targets the correct model.

Instructions

ALWAYS call FIRST at session start. Returns model name, package path, framework directory, project path, environment type, and EXTENSION_PREFIX. Flags placeholder model names and missing prefix. Pass projectName/projectPath when you have the project's name or path. Authoritative source for target model — not search results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
changesNoReturn the uncommitted X++ changes (`git diff HEAD`) plus per-file rollback hints INSTEAD of the configuration. Review-only — not a way to verify a write.
diagnosticsNoInclude verbose sections (config sources, suffix, project paths, index scan, stdio handshake). Use when debugging config or connectivity.
projectNameNoThe PROJECT file name, e.g. "Contoso - FeatureManagement" — pass it whenever you have one: the USER named it, or an earlier call listed it. NOT a model name, and not a guess from a ticket: one model has many projects, so naming it selects none. Steers WRITES only; reads span every model already.
projectPathNoAbsolute path to a .rnrproj file. Use when projectName is ambiguous, none was auto-selected, or D365FO_SOLUTIONS_PATH is unset. Example: "K:\\repos\\Contoso\\MyProject\\MyProject.rnrproj"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.16.2
    • addedInput schema / properties / changes
      Added value: +{
+  "default": false,
+  "description": "Return the uncommitted X++ changes (`git diff HEAD`) plus per-file rollback hints INSTEAD of the configuration. Review-only — not a way to verify a write.",
+  "type": "boolean"
+}
    • changedInput schema / properties / projectName / description
      Previous value: -"Only when the USER says \"switch to <project>\". The PROJECT file name, e.g. \"Contoso - FeatureManagement\". NOT a model name: one model is built by many projects, so naming it selects none and the call is refused. Reads span every model already."New value: +"The PROJECT file name, e.g. \"Contoso - FeatureManagement\" — pass it whenever you have one: the USER named it, or an earlier call listed it. NOT a model name, and not a guess from a ticket: one model has many projects, so naming it selects none. Steers WRITES only; reads span every model already."
    • changedInput schema / properties / projectPath / description
      Previous value: -"Absolute path to a .rnrproj file. Fallback when projectName is ambiguous or D365FO_SOLUTIONS_PATH is not configured. Example: \"K:\\\\repos\\\\Contoso\\\\MyProject\\\\MyProject.rnrproj\""New value: +"Absolute path to a .rnrproj file. Use when projectName is ambiguous, none was auto-selected, or D365FO_SOLUTIONS_PATH is unset. Example: \"K:\\\\repos\\\\Contoso\\\\MyProject\\\\MyProject.rnrproj\""
  2. Changed1 schema field changedv1.10.0
    • changedInput schema / properties / projectName / description
      Previous value: -"Only when the USER says \"switch to <project>\". Just the model name, e.g. \"ContosoEDS\"; path resolved from D365FO_SOLUTIONS_PATH. NOT a way to reach another model — reads span every model already, writes stay in the workspace model."New value: +"Only when the USER says \"switch to <project>\". The PROJECT file name, e.g. \"Contoso - FeatureManagement\". NOT a model name: one model is built by many projects, so naming it selects none and the call is refused. Reads span every model already."
  3. Changed1 schema field changedv1.9.0
    • changedInput schema / properties / diagnostics / description
      Previous value: -"Include verbose diagnostic sections (suffix breakdown, stdio session/handshake dump). Use when debugging client-server connectivity."New value: +"Include verbose sections (config sources, suffix, project paths, index scan, stdio handshake). Use when debugging config or connectivity."
  4. Changed1 schema field changedv1.8.5
    • changedInput schema / properties / projectName / description
      Previous value: -"Preferred way to switch projects. Just the model name, e.g. \"ContosoEDS\" or \"ContosoBank\". The server resolves the full path from D365FO_SOLUTIONS_PATH automatically. Use this when the user says \"switch to <project>\" or opens a different solution."New value: +"Only when the USER says \"switch to <project>\". Just the model name, e.g. \"ContosoEDS\"; path resolved from D365FO_SOLUTIONS_PATH. NOT a way to reach another model — reads span every model already, writes stay in the workspace model."
  5. First observedv1.8.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description reveals useful traits: it flags placeholder model names and missing EXTENSION_PREFIX, is the authoritative source for the target model, and treats the changes parameter as review-only ('not a way to verify a write'). This gives agents expectations about validation and reliability.

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 compact and front-loaded with the most important instruction ('ALWAYS call FIRST at session start'), then lists return values, flags, and source authority in four tight sentences. No filler or repetition.

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

Completeness5/5

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

For a no-output-schema tool, it names the key returned fields, flags edge conditions (placeholder model, missing prefix), and tells the agent where the information sits in the session workflow. Combined with the rich parameter schema, nothing essential is missing.

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 100%, so the input schema already fully documents all four parameters. The description adds only a small usage note about passing projectName/projectPath, but does not materially extend the parameter semantics beyond what the schema provides.

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 names a specific verb and resource ('get workspace info') and states precisely what it returns: model name, package path, framework directory, project path, environment type, and EXTENSION_PREFIX. It also distinguishes itself from siblings by declaring it the 'Authoritative source for target model — not search results,' and by being the mandated first call.

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

Usage Guidelines5/5

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

It gives an explicit invocation rule ('ALWAYS call FIRST at session start'), tells when to pass projectName/projectPath ('when you have the project's name or path'), and warns against using search results for the target model. The schema's diagnostics and changes parameters further state when to use them (debugging vs review-only), so an agent knows when to call this vs alternatives.

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

Deploy Server

Other Tools