PowerPlatform MCP Server

get-global-option-set

Retrieve a global option set definition by its name to inspect available options and metadata for PowerPlatform/Dataverse entities.

Instructions

Get a global option set definition by name

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": {
      "optionSetName": "<optionSetName>"
    },
    "name": "get-global-option-set"
  }
}

Input Schema

Name	Required	Description	Default
`optionSetName`	Yes	The name of the global option set

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.5Jul 31, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It simply says 'Get', indicating a read operation, but does not mention potential errors, permissions, return format, or side effects. The description is minimal and lacks behavioral context beyond the obvious read-only nature.

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?

The description is a single sentence, front-loaded with the core action and resource, with zero extraneous words. It is perfectly concise and well-structured for its simplicity.

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 simple getter with one well-documented parameter and no output schema, the description is adequate. It clearly states the tool's purpose and input. While it could mention return details or failure behavior, the low complexity makes this a minor gap, so it earns a 4 rather than 3.

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 single parameter optionSetName has 100% schema description coverage ('The name of the global option set'). The description's 'by name' aligns with the schema but adds no additional semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 'Get a global option set definition by name' uses a specific verb (Get) and resource (global option set definition), clearly distinguishing it from siblings like get-entity-metadata and get-record. It is unambiguous and directly conveys the tool's function.

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 context is implied by the resource name and sibling tools (e.g., this is for option sets, not entity metadata or records), but there is no explicit guidance on when to use this tool versus alternatives. No exclusions or alternative references are given.

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

Deploy Server