Skip to main content
Glama
dynamics365ninja

D365 F&O MCP Server

by dynamics365ninja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_object_info

Read-only

Retrieve D365 F&O object metadata for tables, classes, forms, queries, and more—single or batch (up to 10) in one parallel call, with optional flags for member lists, method signatures, and AOT XML.

Instructions

Read D365FO object metadata. For 2+ objects pass objects:[{objectType,objectName},…] (max 10) — ONE call, run in parallel, per-object sections back; never loop single calls. One object: {objectType, name}. Pick the kind via objectType: class, table, form, query, view, enum, edt, report, data-entity, menu-item, service, map, config-key, security-policy, macro. Extension types (table-extension, form-extension, enum-extension, edt-extension, data-entity-extension) list all extensions of a base object — pass the base object name or a full extension name (the dot suffix is stripped automatically). Type-specific flags go in options. For CLASSES, {"members":"names"} (optional {"prefix":...}) returns a fast IntelliSense-style member-name list instead of full metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoExact object name (use search first if unsure). REQUIRED unless using objects[].
objectsNoPREFERRED for 2+ objects: read them all in one round trip. Each entry takes the same objectType/options as the single form, with the name in objectName.
optionsNoType-specific reader flags: includeRdl (report), searchControl/maxControls (form), compact/methodOffset (class+table), fieldsOffset/fieldFilter/relations (table), filter (macro), mode (edt), includeFields, includeOperations, modelName. On class/table/view/data-entity, {"method":"validateWrite","include":"signature"} returns ONE method (include: signature | source | both) — required before writing a CoC extension. {"include":"xml"} returns raw AOT XML + its path (page: startLine/endLine) — never shell out to find or read a file. Applies to every objects[] entry.
objectTypeNoKind of object to read. REQUIRED unless using objects[].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.16.2
    • changedInput schema / properties / objects / items / properties / objectType / description
      Previous value: -"Kind of object to read"New value: +"Kind of object to read — same values as the top-level `objectType`."
    • removedInput schema / properties / objects / items / properties / objectType / enum
      Removed value: -[
-  "class",
-  "table",
-  "form",
-  "query",
-  "view",
-  "enum",
-  "edt",
-  "report",
-  "data-entity",
-  "menu-item",
-  "service",
-  "map",
-  "config-key",
-  "security-policy",
-  "macro",
-  "table-extension",
-  "class-extension",
-  "form-extension",
-  "enum-extension",
-  "edt-extension",
-  "data-entity-extension"
-]
    • changedInput schema / properties / options / description
      Previous value: -"Type-specific reader flags: includeRdl (report), searchControl/maxControls (form), compact/methodOffset (class), fieldsOffset/fieldFilter (table), filter (macro), mode (edt), includeFields, includeOperations, modelName. On class/table/view/data-entity, {\"method\":\"validateWrite\",\"include\":\"signature\"} returns ONE method (include: signature | source | both) — required before writing a CoC extension. {\"include\":\"xml\"} returns raw AOT XML + its path (page: startLine/endLine) — never shell out to find or read a file. Applies to every objects[] entry."New value: +"Type-specific reader flags: includeRdl (report), searchControl/maxControls (form), compact/methodOffset (class+table), fieldsOffset/fieldFilter/relations (table), filter (macro), mode (edt), includeFields, includeOperations, modelName. On class/table/view/data-entity, {\"method\":\"validateWrite\",\"include\":\"signature\"} returns ONE method (include: signature | source | both) — required before writing a CoC extension. {\"include\":\"xml\"} returns raw AOT XML + its path (page: startLine/endLine) — never shell out to find or read a file. Applies to every objects[] entry."
  2. Changed2 schema fields changedv1.14.0
    • changedInput schema / properties / objectType / description
      Previous value: -"Kind of object to read (incl. *-extension types — pass base object name or full extension name). REQUIRED unless using objects[]."New value: +"Kind of object to read. REQUIRED unless using objects[]."
    • changedInput schema / properties / objects / items / properties / objectName / description
      Previous value: -"Exact object name (use search first if unsure)"New value: +"Exact object name."
  3. Changed1 schema field changedv1.10.0
    • changedInput schema / properties / options / description
      Previous value: -"Type-specific flags forwarded to the reader: includeRdl, includeFields, searchControl, compact, includeOperations, filter, mode, modelName. For a CLASS, {\"method\":\"validateWrite\",\"include\":\"signature\"} returns ONE method (include: signature | source | both) — required before writing a CoC extension. Big objects are paged — table fieldsOffset/fieldFilter, form maxControls. Applies to every objects[] entry."New value: +"Type-specific reader flags: includeRdl (report), searchControl/maxControls (form), compact/methodOffset (class), fieldsOffset/fieldFilter (table), filter (macro), mode (edt), includeFields, includeOperations, modelName. On class/table/view/data-entity, {\"method\":\"validateWrite\",\"include\":\"signature\"} returns ONE method (include: signature | source | both) — required before writing a CoC extension. {\"include\":\"xml\"} returns raw AOT XML + its path (page: startLine/endLine) — never shell out to find or read a file. Applies to every objects[] entry."
  4. Changed5 schema fields changedv1.9.0
    • changedInput schema / properties / name / description
      Previous value: -"Exact object name (use search first if unsure)"New value: +"Exact object name (use search first if unsure). REQUIRED unless using objects[]."
    • changedInput schema / properties / objectType / description
      Previous value: -"Kind of object to read (incl. *-extension types — pass base object name or full extension name)"New value: +"Kind of object to read (incl. *-extension types — pass base object name or full extension name). REQUIRED unless using objects[]."
    • addedInput schema / properties / objects
      Added value: +{
+  "description": "PREFERRED for 2+ objects: read them all in one round trip. Each entry takes the same objectType/options as the single form, with the name in objectName.",
+  "items": {
+    "properties": {
+      "objectName": {
+        "description": "Exact object name (use search first if unsure)",
+        "type": "string"
+      },
+      "objectType": {
+        "description": "Kind of object to read",
+        "enum": [
+          "class",
+          "table",
+          "form",
+          "query",
+          "view",
+          "enum",
+          "edt",
+          "report",
+          "data-entity",
+          "menu-item",
+          "service",
+          "map",
+          "config-key",
+          "security-policy",
+          "macro",
+          "table-extension",
+          "class-extension",
+          "form-extension",
+          "enum-extension",
+          "edt-extension",
+          "data-entity-extension"
+        ],
+        "type": "string"
+      },
+      "options": {
+        "description": "Optional type-specific flags for this object; overrides the top-level options.",
+        "type": "object"
+      }
+    },
+    "required": [
+      "objectType",
+      "objectName"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / options / description
      Previous value: -"Optional type-specific flags forwarded to the reader (e.g. includeRdl, includeFields, searchControl, compact, includeOperations, filter, mode, modelName)."New value: +"Type-specific flags forwarded to the reader: includeRdl, includeFields, searchControl, compact, includeOperations, filter, mode, modelName. For a CLASS, {\"method\":\"validateWrite\",\"include\":\"signature\"} returns ONE method (include: signature | source | both) — required before writing a CoC extension. Big objects are paged — table fieldsOffset/fieldFilter, form maxControls. Applies to every objects[] entry."
    • removedInput schema / required
      Removed value: -[
-  "objectType",
-  "name"
-]
  5. First observedv1.8.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark readOnlyHint=true, and openWorldHint=false, so the read-only safety profile is established. The description adds substantial behavioral context beyond that: batching with max 10, parallel execution, per-object sections, automatic dot-suffix stripping for extensions, the members shortcut for classes, and the method-signature option needed before writing CoC extensions. This richly discloses how the tool behaves.

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?

The description is long but dense and appropriately front-loaded with the core purpose. Every sentence carries operational value, and guidance like 'never loop single calls' is a necessary addition. It could be slightly improved with clearer visual separation of the many rules, but no sentence is wasted.

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 and high complexity, the description covers the main calling patterns, type taxonomy, extension behavior, and key options. It gives only a high-level picture of return values ('per-object sections back', 'fast IntelliSense-style member-name list'), which is probably sufficient for invocation but leaves some response-shape detail unspecified. Still, the description is complete enough for an agent to select and call the tool correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds significant semantic value beyond the schema: it clarifies that objects[] is the preferred batch form, explains how extension types treat base vs. extension names, lists what each options flag is used for, and gives concrete examples like {"members":"names"} and {"method":"validateWrite","include":"signature"}. This goes well beyond the schema's own descriptions.

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?

The description opens with a specific verb and resource: 'Read D365FO object metadata.' It also enumerates the supported object types and distinguishes the read-oriented purpose from sibling tools by implication. However, it does not explicitly name or contrast any sibling (e.g., search, find_references), so differentiation is clear but not stated.

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 strong operational guidance: use objects[] for 2+ objects, never loop single calls, pass base or full extension names, and use type-specific options. It also includes an explicit 'never shell out' directive. It does not, however, tell the agent when to prefer this tool over specific siblings such as search or find_references, so exclusion guidance is incomplete.

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