Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

create_model_choices

Destructive

Creates a global Dataverse picklist choice within an existing unmanaged solution and publisher prefix, previewing by default, allocating option values, and verifying saved labels and values.

Instructions

Create a global Picklist choice with an existing unmanaged solution and publisher prefix. Default preview. Omit option value to request native publisher-based allocation; supplied numeric values and label sets must be unique. Verifies saved labels and allocated values; no automatic 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.
optionsNo
schemaNameNo
descriptionNo
displayNameNo
schema_nameNo
display_nameNo
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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, and the description adds real context beyond that: default preview mode before execution, validation of saved labels and allocated values, uniqueness constraints on values and label sets, and the fact that nothing is published automatically.

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 verb and resource, then operational constraints in short clauses; no filler sentences. A few phrases are telegraphic ('Default preview', 'no automatic publication'), which costs a little clarity but not much length.

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 mutation with 11 parameters and no output schema, the definition covers the critical operational facts: preview default, allocation behavior, uniqueness, publisher-prefix validation, post-write verification, and no automatic publish. The shape of the verification result and the concrete follow-up (publishing) are only alluded to, leaving a small gap.

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?

With only 45% schema description coverage, the description compensates on the important pieces: omitting `value` requests native publisher-based allocation, supplied numeric values and label sets must be unique, and the solution parameter must be an existing unmanaged solution whose publisher prefix is validated. It says nothing extra about schema_name/display_name, but those are self-evident from the schema patterns.

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?

States a specific verb and resource: creating a global Picklist choice, constrained to an existing unmanaged solution whose publisher prefix is validated. The trailing 'no automatic publication' implicitly distinguishes it from publish_model_choices, but no sibling is named explicitly.

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?

Usage is implied rather than stated: 'Default preview' tells the agent the default is a dry run and 'no automatic publication' hints a later publish step is required, but the description never tells the agent when to prefer this over change_model_choice_value or publish_model_choices, nor what prerequisites (unmanaged solution only) exclude.

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