Skip to main content
Glama

get_object_info

Read-only

Retrieves D365 F&O object metadata for one or up to 10 objects in a single parallel batch call, returning type-specific details.

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, menu, service, map, config-key, security-policy, macro, model. The *-extension types 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.

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": "get_object_info"
  }
}

Input 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. Changed1 schema field changedv1.25.0
    • changedInput schema / properties / objectType / enum
      Previous value: -[
      -  "class",
      -  "table",
      -  "form",
      -  "query",
      -  "view",
      -  "enum",
      -  "edt",
      -  "report",
      -  "data-entity",
      -  "menu-item",
      -  "menu",
      -  "service",
      -  "map",
      -  "config-key",
      -  "security-policy",
      -  "macro",
      -  "table-extension",
      -  "class-extension",
      -  "form-extension",
      -  "enum-extension",
      -  "edt-extension",
      -  "data-entity-extension",
      -  "menu-extension"
      -]New value: +[
      +  "class",
      +  "table",
      +  "form",
      +  "query",
      +  "view",
      +  "enum",
      +  "edt",
      +  "report",
      +  "data-entity",
      +  "menu-item",
      +  "menu",
      +  "service",
      +  "map",
      +  "config-key",
      +  "security-policy",
      +  "macro",
      +  "model",
      +  "table-extension",
      +  "class-extension",
      +  "form-extension",
      +  "enum-extension",
      +  "edt-extension",
      +  "data-entity-extension",
      +  "menu-extension"
      +]
  2. Changed1 schema field changedv1.24.0
    • changedInput schema / properties / objectType / enum
      Previous 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"
      -]New value: +[
      +  "class",
      +  "table",
      +  "form",
      +  "query",
      +  "view",
      +  "enum",
      +  "edt",
      +  "report",
      +  "data-entity",
      +  "menu-item",
      +  "menu",
      +  "service",
      +  "map",
      +  "config-key",
      +  "security-policy",
      +  "macro",
      +  "table-extension",
      +  "class-extension",
      +  "form-extension",
      +  "enum-extension",
      +  "edt-extension",
      +  "data-entity-extension",
      +  "menu-extension"
      +]
  3. 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."
  4. 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."
  5. 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."
  6. 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"
      -]
  7. First observedv1.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavior beyond that — max 10 objects per call, per-object sections returned, automatic stripping of the dot suffix on extension names, and a notably faster reduced-payload mode for class members. It does not describe error behavior or how partial failures across a batch are reported.

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?

Front-loaded with the core action and the batching rule before drilling into per-type detail, which is the right order for an agent skimming. It is dense but nearly every clause carries operational information; the long parenthetical flag lists make it heavier to scan than necessary.

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?

Covers the essentials for a nested-schema, no-output-schema reader: dual calling forms, the 10-item cap, the extension-name normalization, and the shortcuts that avoid extra round trips. What is missing is modest — return envelope shape beyond 'per-object sections', and how failures surface — but an agent could invoke this correctly from what is written.

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 schema already carries the type-specific flags, method/include semantics, and xml mode; the description largely mirrors those. It still adds meaning the schema does not: the '*-extension' object types accept either a base name or a full extension name with the suffix auto-stripped, and {"members":"names"} with optional prefix returns a name-only IntelliSense list rather than full metadata.

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?

Opens with a specific verb+resource: 'Read D365FO object metadata', then enumerates the supported object kinds, so an agent knows exactly what domain this covers. It does not explicitly route away from close siblings such as search or extension_info, even though the '*-extension types' feature plausibly overlaps with extension_info — that ambiguity is the only thing keeping it from a 5.

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 concrete when-to guidance: use objects[] for 2+ objects in ONE parallel call and 'never loop single calls', use members+prefix for a fast class member listing, use the method/include form before writing a CoC extension. It also forbids an anti-pattern ('never shell out to find or read a file'). It stops short of naming sibling tools or stating when this tool is the wrong choice.

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