Skip to main content
Glama

object_patterns

Read-only

Get D365 F&O pattern guidance by domain: table field/index/relation patterns, form recommendations/specs/XML validation, report recipes, and mobile app screen recipes.

Instructions

Pattern toolkit. Choose a domain: • table → field/index/relation patterns for D365FO tables. Filter by tableGroup or similarTo a given table. • form → form-pattern toolkit; pick an action:

  • analyze → pattern advisor + usage analysis. For a NEW form pass recommend (preferred): the Microsoft decision tree picks the pattern and names reference forms to clone. Or filter by formPattern / dataSource / similarTo.

  • spec → structure spec of a pattern/sub-pattern: hierarchy, ordering, allowed children, reference forms, lifecycle.

  • validate → AxForm XML validator (hierarchy/order, sub-patterns, PatternVersion) → FP001-FP011. Call before d365fo_file action=create. • report → SSRS implementation recipes: object roster, scaffold call, checks. Optional pattern=. • mobile-app → warehouse-app screen recipes, led by the choice between the two frameworks that build them (ProcessGuide vs WHSWorkExecuteDisplay): create a flow, add or replace one screen, step icon/title, GS1 scan input. Optional pattern=.

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

Input Schema

NameRequiredDescriptionDefault
xmlNo[validate] Complete AxForm XML to validate. Provide this OR formName/filePath.
limitNo[analyze] Max pattern examples.
actionNo[form] Which form-pattern operation to run. repair = auto-fill missing required controls.
domainNoOptional — inferred from the other params (action/pattern/xml/formName → form; tableGroup → table). A concept like "number-sequence" is not a domain: that is get_knowledge.
patternNo[spec|report|mobile-app] Pattern name (id, xmlName or alias) — e.g. "SimpleList", "FieldsFieldGroups", "PrintMgmtFormLetter", "processguide-flow".
filePathNo[form/validate] Path to an AxForm XML file not yet indexed.
formNameNo[validate] Name of an indexed form — XML is loaded from the metadata store.
recommendNo[analyze] Pattern advisor: describe requirements, get a recommended pattern + reference forms to clone.
similarToNo[table] table / [form-analyze] form name to find similar patterns.
dataSourceNo[form/analyze] Table name - find forms using this table
tableGroupNo[table] Table group type to analyze (choose one).
formPatternNo[analyze] D365FO form pattern to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.16.2
    • changedInput schema / properties / domain / description
      Previous value: -"table = table field/index/relation patterns; form = form-pattern toolkit (set action). Optional — inferred from the other params (action/pattern/xml/formName → form; tableGroup → table). ⚠️ This is NOT a free-form \"pattern type\": a concept like \"number-sequence\"/\"SysOperation\" belongs to get_knowledge, not here."New value: +"Optional — inferred from the other params (action/pattern/xml/formName → form; tableGroup → table). A concept like \"number-sequence\" is not a domain: that is get_knowledge."
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "table",
      -  "form"
      -]New value: +[
      +  "table",
      +  "form",
      +  "report",
      +  "mobile-app"
      +]
    • changedInput schema / properties / filePath / description
      Previous value: -"[form/validate] Explicit path to an AxForm XML file (e.g. a freshly created form not yet indexed)."New value: +"[form/validate] Path to an AxForm XML file not yet indexed."
    • changedInput schema / properties / limit / description
      Previous value: -"[analyze] Maximum number of pattern examples (default: 10)"New value: +"[analyze] Max pattern examples."
    • changedInput schema / properties / pattern / description
      Previous value: -"[spec] REQUIRED. Pattern name (id, xmlName, or alias) — e.g. \"SimpleList\", \"DetailsMaster\", or a sub-pattern like \"FieldsFieldGroups\"."New value: +"[spec|report|mobile-app] Pattern name (id, xmlName or alias) — e.g. \"SimpleList\", \"FieldsFieldGroups\", \"PrintMgmtFormLetter\", \"processguide-flow\"."
    • changedInput schema / properties / similarTo / description
      Previous value: -"[table] table name to find similar table patterns; [form/analyze] form name to find similar form patterns."New value: +"[table] table / [form-analyze] form name to find similar patterns."
  2. Changed3 schema fields changedv1.14.0
    • changedInput schema / properties / recommend / properties / entityKind / description
      Previous value: -"Kind of entity: master (customers), transaction (orders+lines), setup (group tables), parameters, inquiry (read-only), lookup, workspace, dialogTask"New value: +"Kind of entity being modelled."
    • changedInput schema / properties / recommend / properties / fieldCount / description
      Previous value: -"Approximate fields users see/edit per record (<10 → SimpleList, ≥10 → SimpleListDetails)"New value: +"Approximate fields users see/edit per record."
    • changedInput schema / properties / recommend / properties / tableName / description
      Previous value: -"Main table — pulls field count and existing-form evidence from the index"New value: +"Main table — pulls field count and existing-form evidence from the index."
  3. First observedv1.8.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a read-only advisory tool. Beyond that it discloses useful traits: validate emits FP001-FP011 hierarchy/order findings, analyze returns a decision-tree recommendation plus reference forms to clone, and spec returns hierarchy/ordering/allowed-children data. Minor gaps remain – the enum's 'repair' action (auto-fill of required controls) appears only in the schema, not in the description's action list, and no volume or performance expectations are set for large pattern sets.

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 bulleted domain→action structure is front-loaded and scannable, with tags like [validate] and [analyze] mapping cleanly onto parameters. It is dense and somewhat long for a description, but nearly every clause carries routing or behavioral information; the only questionable space is repeated mentions of optional pattern=<id> for report and mobile-app.

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 12-parameter, zero-required, multi-mode tool with a nested object and no output schema, the description covers what each mode does and when to invoke it, which is the burden it must carry. The gaps are modest: the repair action is unmentioned in the description text and return shapes are characterized only loosely (advisor output, spec hierarchy, FP001-FP011 codes) rather than with the field set an agent could expect.

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, but the description adds real meaning on top: it explains domain inference from other parameters (action/pattern/xml/formName → form; tableGroup → table), per-branch applicability tags for pattern, similarTo, and dataSource, and gives concrete pattern-name examples ('SimpleList', 'PrintMgmtFormLetter', 'processguide-flow'). The nested recommend object is characterized as a requirements description feeding a Microsoft decision tree, which the schema fields alone would not convey.

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 opening 'Pattern toolkit' is vague, but the bullets immediately enumerate the four domains (table, form, report, mobile-app) and the per-domain operations, so an agent can tell this covers pattern selection, structure specs, and AxForm validation rather than plain metadata lookup. It is distinguishable from siblings like get_object_info or d365fo_file, though the generic name means the goal only becomes clear after reading the bullet list.

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?

Explicit routing is provided at every branch: choose a domain, and for forms pick analyze/spec/validate with the condition for each ('For a NEW form pass recommend (preferred)', 'Call before d365fo_file action=create'). It also names the fallback path ('a concept like "number-sequence" is not a domain: that is get_knowledge') and contrasts similarTo/formPattern/dataSource filters, leaving little to inference.

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