Skip to main content
Glama

Power Automate MCP Server by Flow Studio

by io.github.ninihen1
OverviewDiscussionsAdmin

list_live_environments

Read-only

List all Power Platform environments you belong to, directly from Power Automate. Returns id, displayName, sku, location, and state for each environment. mode=all (default) and mode=member: every environment you are a member of. mode=admin: only those you administer; errors rather than guessing if admin access cannot be determined. isAdmin means you hold the ListAnyFlow permission there — the capability list_live_flows mode=admin needs. It is null, never false, when the platform did not tell us. isMember is true for every environment returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax environments to return. Paginates automatically. Omit for all.
modeNoall (default) and member: every environment you belong to. admin: only those where you hold ListAnyFlow; errors rather than returning a shorter list if admin access cannot be determined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"all (default): member + admin environments merged. member: member-scoped only, skips the admin sweep. admin: admin-scoped only, and a refused admin scope is reported as an error rather than silently omitted."New value: +"all (default) and member: every environment you belong to. admin: only those where you hold ListAnyFlow; errors rather than returning a shorter list if admin access cannot be determined."
  2. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "all (default): member + admin environments merged. member: member-scoped only, skips the admin sweep. admin: admin-scoped only, and a refused admin scope is reported as an error rather than silently omitted.",
+  "enum": [
+    "all",
+    "member",
+    "admin"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds transparency by specifying that mode=admin errors if access cannot be determined, and explains the semantic of isAdmin and isMember fields.

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?

The description is well-structured with a summary and parameter details, but the mode explanation is repeated verbatim in the top-level description and parameter description, adding minor redundancy.

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?

The description mentions the return fields (id, displayName, sku, location, state) and explains mode semantics sufficiently. No output schema is provided, but the description covers necessary context for a read-only list operation.

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

Parameters5/5

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

Schema coverage is 100% and the description enriches both parameters: top explains pagination and omission default; mode explains each enum value and the admin error case.

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?

Clearly states the verb 'list' and resource 'Power Platform environments', with return fields listed. Distinguishes from sibling list_store_environments by specifying 'live' directly from Power Automate.

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

Usage Guidelines4/5

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

Provides explicit guidance on mode parameter values, defaults, and error behavior. Does not explicitly name alternative sibling tools, but the 'live' vs 'store' naming implies the distinction, and the mode conditions are clear.

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

All Power Automate MCP Server by Flow Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources