power-automate-mcp

list-connections

List connector connections in an environment to obtain IDs, names, and statuses for building connectionReferences in flow creation or update.

Instructions

List the connector connections in an environment (id, connector, display name, status). Use these ids to build the connectionReferences for create-flow / update-flow -- e.g. the shared_office365 connection for mail/calendar Graph calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-connections"
  }
}

Input Schema

Name	Required	Description	Default
`environment`	No	Environment id (defaults to POWER_AUTOMATE_ENV)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 30, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It implies a read-only list operation but does not mention any potential side effects, authentication requirements, rate limits, or pagination. The simple nature of listing connections mitigates some concerns, but more transparency would improve the score.

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 extremely concise: two sentences that front-load the core purpose and then provide a usage hint. Every sentence adds value without redundancy.

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

Completeness4/5

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

Given the low complexity (one optional parameter, no output schema, no nested objects), the description covers the essential purpose and usage. The first sentence lists return fields, which partially compensates for the lack of an output schema. However, it could mention the return type or any pagination behavior for completeness.

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 100% for the single optional parameter 'environment', which already has a description. The tool description does not add additional semantic information about the parameter beyond what is in the schema, so baseline 3 is appropriate.

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 clearly states it lists connector connections and specifies the fields returned (id, connector, display name, status). While it doesn't explicitly distinguish from sibling list tools like list-flows, the resource is uniquely identified, making purpose clear.

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?

The description explicitly says to use the ids for create-flow / update-flow and provides a concrete example (shared_office365 connection). This gives clear guidance on when and why to use this tool.

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

Deploy Server