Skip to main content
Glama

Power Automate MCP Server by Flow Studio

by io.github.ninihen1
OverviewDiscussionsAdmin

describe_live_connector

Read-only

Describe a live Power Platform connector/API and its operations. Aligned with Canvas MCP describe_api. Use mode=summary (default) to get a compact operation catalog. Use operationId to describe one operation, including inputs, outputs, dynamic parameter metadata, nextTool hints to call resolve_live_parameters, and an authored hint + canonical example shape (when one exists) to copy into update_live_flow. Use search without connectorName/apiName to search operations across connectors and get connection-aware suggestions. Use mode=full only when raw OpenAPI connector metadata is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMax operations to return in connector summary mode, or max top search results to show in cross-connector search. Default 250 for summary, 10 for search display.
modeNosummary (default): compact operation catalog. full: raw OpenAPI metadata.
typeNoOperation usage to include in summary mode. Default Action.
searchNoOptional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors.
apiNameNoAlias for connectorName, matching Canvas MCP describe_api naming.
variantNoWhen an operation has multiple authored variants (e.g. shared_teams/PostMessageToConversation has channel/groupchat/flowbot_chat), pass a specific variantKey to get that variant's hint and exampleDefinition. Omit to receive a hint listing the available variants.
operationIdNoOptional operation ID to describe with expanded inputs and outputs.
connectorNameNoConnector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search.
environmentNameYesName of the Power Platform environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / connectorName / description
      Previous value: -"Connector logical name, for example shared_teams. Either connectorName or apiName is required."New value: +"Connector logical name, for example shared_teams. Either connectorName/apiName is required, unless search is provided for cross-connector operation search."
    • changedInput schema / properties / search / description
      Previous value: -"Optional operation search text applied to name, summary, description, tags, and visibility."New value: +"Optional operation search text. With connectorName, filters that connector summary. Without connectorName, searches operations across connectors."
    • changedInput schema / properties / top / description
      Previous value: -"Max operations to return in summary mode. Default 250."New value: +"Max operations to return in connector summary mode, or max top search results to show in cross-connector search. Default 250 for summary, 10 for search display."
  2. Changed1 schema field changed
    • addedInput schema / properties / variant
      Added value: +{
+  "description": "When an operation has multiple authored variants (e.g. shared_teams/PostMessageToConversation has channel/groupchat/flowbot_chat), pass a specific variantKey to get that variant's hint and exampleDefinition. Omit to receive a hint listing the available variants.",
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral detail beyond annotations: what each mode returns, that operationId includes dynamic parameter metadata, that nextTool hints route to resolve_live_parameters, and that variant handling exists for authored variants like shared_teams/PostMessageToConversation.

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 dense but every sentence earns its place. It front-loads the primary purpose and then systematically explains mode usage, search behavior, and when to use full mode, without repeating schema field descriptions or filler.

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?

There is no output schema, so the description carries the burden of explaining return value semantics. It covers the compact catalog, expanded operation details, dynamic parameter metadata, nextTool hints, and canonical example shapes, while also linking to sibling tools. The parameter interactions are sufficiently covered by the schema and description together.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds combinatorial and workflow semantics: how mode, operationId, search, connectorName/apiName, and variant interact, and what each returns. It clarifies that connectorName/apiName can be omitted when search is used, and that full mode is for raw metadata only.

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?

States a specific verb and resource: 'Describe a live Power Platform connector/API and its operations.' It clearly distinguishes the tool by its modes (summary, operationId, cross-connector search, full) and references alignment with Canvas MCP describe_api, making its purpose immediately identifiable relative to sibling get/list tools.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance for each mode: mode=summary for a compact catalog, operationId for one operation, search without connectorName/apiName for cross-connector search, and mode=full only when raw OpenAPI metadata is required. It also names downstream tools (resolve_live_parameters, update_live_flow), giving practical routing context.

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