Skip to main content
Glama
laveeshb

logicapps-mcp

by laveeshb

validate_clone_workflow

Validate whether a Consumption Logic App workflow can be cloned to a Standard Logic App. Identifies unsupported operations and compatibility issues before cloning.

Instructions

Validate if a Consumption Logic App workflow can be cloned to a Standard Logic App without actually performing the clone. This checks for unsupported operations, connection compatibility, and other potential issues. Use this before clone_workflow to identify any problems that need to be addressed.

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')
Behavior3/5

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

The description discloses the tool's non-destructive nature (validates without cloning) and checks performed, but with no annotations available, it omits details like authentication needs, rate limits, or how results are returned, leaving gaps for an agent.

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?

Two clear, front-loaded sentences with zero waste. Every sentence adds value, efficiently conveying purpose and usage.

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 no output schema and 8 parameters, the description covers the main purpose and usage but lacks detail on the return value format or error handling, which would be helpful for complete understanding.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it does not elaborate on any parameters individually.

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 clearly states the tool validates cloning feasibility without performing the clone, distinguishes from sibling clone_workflow by specifying it is a pre-check, and lists what it checks (unsupported operations, connection compatibility).

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?

Explicitly says to use this tool before clone_workflow to identify issues, providing clear usage context. However, it does not mention when not to use this tool or alternative scenarios, missing an explicit exclusion.

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