Skip to main content
Glama
Sign In
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_cloud_flow_runs

Read-only

Retrieves bounded Dataverse run metadata for a cloud flow, enabling inspection of recent executions while noting results may be delayed or incomplete.

Instructions

Read bounded Dataverse run metadata for a cloud flow. Results may be delayed, unavailable or incomplete and do not establish full runtime history.

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>"
    },
    "name": "list_cloud_flow_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
topNo
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

B3.3/5.0
Behavior4/5

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

The readOnlyHint already establishes safety, but the description adds useful behavioral context beyond annotations: results may be delayed, unavailable, or incomplete and do not establish full runtime history. It still does not explain the 'bounded' result set or pagination behavior, which keeps it from a 5.

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 two tightly written sentences with the core operation front-loaded and no wasted wording. The reliability caveat is compact and relevant.

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?

The description covers scope and reliability well enough for a read-only listing tool whose safety profile is already in annotations. However, with no output schema and low parameter documentation, it leaves gaps around what run metadata is returned and how id, top, and environment_profile affect the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one of three parameters, environment_profile, is documented in the schema, and the description does not mention id or top at all. It implies that the operation is scoped to a cloud flow, but does not compensate for the low schema coverage by explaining required identifiers or limit semantics.

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 uses a specific verb and resource: 'Read bounded Dataverse run metadata for a cloud flow.' It cleanly distinguishes this from siblings like get_cloud_flow or list_cloud_flows, though it does not explicitly name or compare those alternatives.

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?

There is no explicit guidance on when to use this tool versus related cloud flow tools such as get_cloud_flow, list_cloud_flows, or set_cloud_flow_state. The caveat about delayed or incomplete results describes reliability, not usage conditions or exclusions.

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