Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

get_field_picklist_options

Retrieve OptionSet (enum) definitions for a specific entity field, including local and global picklists, to inspect allowed values before querying or updating records.

Instructions

Get OptionSet (enum) definitions for a specific field within an entity. Supports both local and global OptionSets.

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": {
      "logical_name": "<logical_name>",
      "attribute_name": "<attribute_name>"
    },
    "name": "get_field_picklist_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
logical_nameYesLogical name of the entity
attribute_nameYesLogical name of the attribute (field)
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

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

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. Its only addition is that it supports both local and global OptionSets, which is genuinely useful scope information for an agent. However, it does not say what the call returns, whether it is read-only, or what happens if the attribute is not a choice field, leaving the main behavioral profile undisclosed.

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?

Two short sentences are front-loaded with the core purpose and followed by a useful scope note. There is no redundant wording, although the definition is too thin to earn a top score.

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?

This is a simple read-style lookup with a small, fully described parameter set, which lowers the bar. However, with no annotations and no output schema, the description should explain what comes back from an OptionSet lookup (for example, option values and labels) and clarify the difference between local and global OptionSets. It does not, so an agent must infer the call's behavior.

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?

The schema description coverage is 100%, and all three parameters are described in the schema. The description only restates that the call needs a field within an entity, adding nothing about formats, naming conventions, or handling of the optional environment_profile parameter. A baseline score of 3 is appropriate because the schema does the work.

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 description gives a specific verb and resource: get OptionSet (enum) definitions for a specific field within an entity. This is a clear purpose, but it does not distinguish this tool from similar retrieval tools in the list, such as get_model_choices or list_model_choices, so an agent must also read those schemas to choose correctly.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool instead of alternatives or on when it should not be used. It also says nothing about prerequisites, such as whether the field must actually be a picklist or choice field before calling it.

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