Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

create_model_key

Destructive

Creates a native alternate-key definition for 1–16 columns, with dry-run preview and validation for solution, field security, duplicates, and index eligibility before execution.

Instructions

Create a native alternate-key definition on 1–16 columns with solution/publisher, type, field-security and duplicate checks. Default preview; server validates index size and existing uniqueness asynchronously. Pending/unknown is not Active. No record scan, index reactivation, save replay or implicit publication.

Input Schema

NameRequiredDescriptionDefault
dryRunNoDefault true performs reads/eligibility checks and returns a native request preview. Set false to execute.
dry_runNoDefault true performs reads/eligibility checks and returns a native request preview. Set false to execute.
schemaNameNo
displayNameNo
logicalNameNo
schema_nameNo
display_nameNo
logical_nameNo
keyAttributesNo
key_attributesNo
solutionUniqueNameNoExisting unmanaged solution; its publisher prefix is validated for new schemas.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
solution_unique_nameNoExisting unmanaged solution; its publisher prefix is validated for new schemas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real value beyond them: async server-side validation of index size and uniqueness, the meaning of pending/unknown versus Active, and the preview-first default. It doesn't say how to poll or confirm the async outcome, which is the remaining gap for a destructive mutation.

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 core action is front-loaded in the first clause, and the remaining sentences are dense but each carries distinct information (preview default, async validation, pending semantics, excluded operations). The telegraphic style ("No record scan, index reactivation, save replay or implicit publication") is slightly clipped but not padded.

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

Completeness3/5

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

For a destructive, non-idempotent mutation with no output schema and low schema coverage, the description covers side effects and the dry-run contract well. It leaves unanswered how the agent verifies the asynchronous validation result and whether prerequisite permissions or an existing solution are required before execution.

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

Parameters2/5

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

With schema coverage at only 38% across 13 parameters, the description needs to compensate and largely doesn't. It clarifies the 1–16 column cap on key_attributes and the publisher-prefix validation for the solution parameter, but says nothing about the snake_case/camelCase alias pairs, the display_name localization structure, or environment_profile.

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 opens with a specific verb+resource: "Create a native alternate-key definition on 1–16 columns," and names the exact scope (solution/publisher, type, field-security, duplicate checks). It also implicitly separates itself from the sibling reactivate_model_key by explicitly excluding "index reactivation."

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?

It gives a clear operational rule: "Default preview" and dry_run=false to execute, plus explicit exclusions (no record scan, no index reactivation, no save replay, no implicit publication). It stops short of naming alternatives — e.g. pointing to reactivate_model_key or get_model_key for the excluded cases — so the agent must infer those routes.

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