Skip to main content
Glama

validate_object_naming

Read-only

Validate proposed Dynamics 365 Finance and Operations object names against extension formats, ISV prefixes, type suffixes, and symbol-index conflicts before use.

Instructions

Validate a proposed D365FO object name: extension naming/formats, ISV prefix, type suffixes, conflicts in the symbol index.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "proposedName": "<proposedName>",
      "objectType": "<objectType>"
    },
    "name": "validate_object_naming"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectTypeYes
modelPrefixNoISV/model prefix (e.g. "WHS"); auto-detected if omitted.
proposedNameYesThe proposed object name to validate
baseObjectNameNoExtension types: the object being extended
baseObjectTypeNoclass-extension: its type (class|table|form|…); picks the name format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.22.0
    • changedInput schema / properties / baseObjectName / description
      Previous value: -"Required for extension types: name of the object being extended"New value: +"Extension types: the object being extended"
    • addedInput schema / properties / baseObjectType
      Added value: +{
      +  "description": "class-extension: its type (class|table|form|…); picks the name format",
      +  "type": "string"
      +}
    • changedInput schema / properties / modelPrefix / description
      Previous value: -"Expected ISV/model prefix (2-4 uppercase letters, e.g. \"WHS\"). Auto-detected if omitted."New value: +"ISV/model prefix (e.g. \"WHS\"); auto-detected if omitted."
    • removedInput schema / properties / objectType / description
      Removed value: -"Type of the D365FO object"
  2. Changed1 schema field changedv1.16.2
    • changedInput schema / properties / objectType / enum
      Previous value: -[
      -  "class",
      -  "table",
      -  "form",
      -  "enum",
      -  "edt",
      -  "query",
      -  "view",
      -  "table-extension",
      -  "class-extension",
      -  "form-extension",
      -  "enum-extension",
      -  "edt-extension",
      -  "menu-item",
      -  "security-privilege",
      -  "security-duty",
      -  "security-role",
      -  "data-entity"
      -]New value: +[
      +  "class",
      +  "table",
      +  "form",
      +  "enum",
      +  "edt",
      +  "query",
      +  "view",
      +  "report",
      +  "table-extension",
      +  "class-extension",
      +  "form-extension",
      +  "enum-extension",
      +  "edt-extension",
      +  "menu-item",
      +  "security-privilege",
      +  "security-duty",
      +  "security-role",
      +  "data-entity"
      +]
  3. First observedv1.8.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by revealing that validation consults the symbol index (i.e., checks live workspace state, not just syntax), but it does not say whether the result is advisory or blocking, or what it reports on a conflict.

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?

One front-loaded sentence with a colon-delimited list of check categories; no filler, no restatement of the title or annotations.

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?

Given a read-only, non-open-world tool with no output schema, the definition covers inputs and validation scope well. The one real gap is the return shape — whether it yields pass/fail, messages, or suggested fixes — which an agent must discover by calling it.

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 80%, so the schema already carries most parameter meaning, including modelPrefix auto-detection and baseObjectType's role in picking the name format. The description reinforces which parameters matter for extension cases (extension naming, ISV prefix) but adds no format syntax or examples beyond the schema.

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?

States a specific verb (validate) and resource (a proposed D365FO object name) and enumerates the exact rule families checked: extension naming/format, ISV prefix, type suffixes, and symbol-index conflicts. That scope is clearly distinct from siblings such as validate_code, generate_object, and object_patterns, so an agent can route to it without opening the schema.

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

Usage Guidelines3/5

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

The description implies the pre-creation use case (checking a 'proposed' name) but never states it explicitly, nor does it name alternatives like generate_object or object_patterns, or say what to do when validation fails. Usage is inferable rather than prescribed.

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