Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_cloud_flow_state

Preview, then enable or disable an Online cloud flow using a native ETag and independent state readback to verify the intended state change before applying it.

Instructions

Preview then enable or disable an Online cloud flow using specific native ETag and independent state readback. Does not establish connection, license or runtime readiness.

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": {
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "set_cloud_flow_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dry_runNo
enabledYes
expected_hashNo
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds real value beyond them: an opt-in preview path, native ETag concurrency control, and an independent state readback after the change, plus an explicit statement of what it does not guarantee.

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, front-loaded with the action and the preview-then-apply ordering. The caveat sentence earns its place by preventing false assumptions about readiness. Slight density/jargon ('native ETag', 'independent state readback') costs a point.

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?

Five parameters with no output schema and low schema coverage demand more from the description. It covers the preview/ETag/readback concept but leaves gaps on what happens when expected_hash does not match, whether disabling is reversible, and what the readback returns.

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 coverage is only 20% (just environment_profile), so the description must compensate. It conveys the meaning of dry_run ('Preview'), enabled ('enable or disable'), and expected_hash ('specific native ETag'), but never maps these to parameter names or explains ETag mismatch behavior, and says nothing about id.

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 pair (enable/disable) on a specific resource (an Online cloud flow), and adds that the operation is preview-then-apply. It is reasonably distinguishable from siblings like update_cloud_flow or prepare_cloud_flow, though it never names an alternative 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 word 'Preview then' implies the intended dry_run-first workflow, but the description gives no explicit when-to-use/when-not guidance and never contrasts this with update_cloud_flow or prepare_cloud_flow. The closing sentence is a scope caveat (connection/license/runtime readiness), not routing guidance.

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