Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

prepare_cloud_flow

Read-only

Builds a local cloud-flow draft for manual, scheduled, or Dataverse event triggers with bounded literals, variables, conditions, and loops; does not contact Power Platform or validate deployment.

Instructions

Construct a local manual, scheduled or Dataverse event cloud-flow draft with bounded literals, variables, condition and foreach. Does not contact Power Platform or validate deployment.

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": {
      "name": "<name>",
      "trigger": "<trigger>",
      "actions": "<actions>"
    },
    "name": "prepare_cloud_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
actionsYes
triggerYes
environment_profileNoOptional named environment profile for this call; omit to use the configured default.
dataverse_connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds meaningful behavior beyond that by clarifying the output is a local draft, that no Power Platform call occurs, and that no deployment validation happens. It does not describe what the returned draft looks like or how it is consumed, which is the remaining gap.

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 tight sentences that front-load the capability and then the key constraint. The middle phrase ('bounded literals, variables, condition and foreach') is compressed to the point of being jargon-heavy but still earns its space.

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

Completeness5/5

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

Placeholder.

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 only 20%, so the description carries real burden; it partially compensates by mapping 'manual, scheduled or Dataverse event' to trigger.kind and 'bounded literals, variables, condition and foreach' to the action kinds. It says nothing about name, actions nesting/ordering, environment_profile, or dataverse_connection, leaving most parameters unexplained.

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 ('Construct a ... cloud-flow draft') and enumerates the supported trigger shapes (manual, scheduled, Dataverse event) and action constructs. The phrase 'local ... draft' plus 'Does not contact Power Platform' implicitly separates it from create_cloud_flow, though 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?

The negative constraint ('does not contact Power Platform or validate deployment') signals this is a drafting step, implying it should precede deployment via create_cloud_flow, but the description never states that workflow or tells the agent when to pick this over create_cloud_flow/update_cloud_flow.

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