Skip to main content
Glama
laveeshb

logicapps-mcp

by laveeshb

clone_workflow

Clone a workflow from Consumption to Standard Logic App by copying its definition. Validate compatibility before cloning.

Instructions

Clone a Consumption Logic App workflow to a Standard Logic App. IMPORTANT: Always run validate_clone_workflow first to check for compatibility issues before cloning. This copies the workflow definition from a Consumption Logic App to a new workflow in an existing Standard Logic App. The target Standard Logic App must already exist and the target workflow name must not already exist. Connections will need to be reconfigured after cloning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesSource Consumption Logic App subscription ID
resourceGroupNameYesSource Consumption Logic App resource group name
logicAppNameYesSource Consumption Logic App name
targetSubscriptionIdNoTarget Standard Logic App subscription ID (defaults to source subscription if not provided)
targetResourceGroupNameYesTarget Standard Logic App resource group name
targetLogicAppNameYesTarget Standard Logic App name (must already exist)
targetWorkflowNameYesName for the new workflow in the Standard Logic App
targetKindNoWorkflow kind for the target (default: 'Stateful')
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that the target must exist, workflow name must be new, and connections need reconfiguration. Implies non-destructive cloning, though not explicitly stated. Could mention that the source workflow is not modified. Overall transparent enough for agent to understand behavior.

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?

Four sentences, each serving a distinct purpose: purpose statement, critical prerequisite, workflow context, and post-cloning action. No fluff. Could be slightly shorter by combining sentences, but current structure is clear and front-loaded with the important warning.

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 the input and process well but lacks any mention of return value or output behavior. Since no output schema exists, the agent would need to know whether the tool returns the cloned workflow details, a success status, or something else. Also, no indication of asynchronous execution or expected duration. This gap reduces completeness for a tool with 8 parameters.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the default behavior for targetSubscriptionId and targetKind, and emphasizing prerequisites for target parameters. This helps the agent understand defaults and constraints beyond the schema.

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?

The description uses a specific verb 'clone' and clearly identifies the resources involved: Consumption Logic App workflow to Standard Logic App. It distinguishes from siblings like create_workflow and validate_clone_workflow by focusing on the migration scenario.

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?

Explicitly instructs to run validate_clone_workflow first for compatibility checks. States preconditions (target Standard must exist, target workflow name must not exist) and post-cloning step (reconfigure connections). The description also mentions that targetSubscriptionId defaults to source subscription and targetKind defaults to Stateful, guiding parameter choices.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laveeshb/logicapps-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server