Skip to main content
Glama
laveeshb

logicapps-mcp

by laveeshb

create_workflow

Creates an Azure Logic Apps workflow. For Consumption SKU, provisions a new Logic App resource; for Standard SKU, adds a workflow to an existing app using a definition JSON.

Instructions

Create a new workflow. For Consumption SKU, creates a new Logic App resource. For Standard SKU, creates a new workflow within an existing Logic App. Requires a valid workflow definition JSON that follows the Logic Apps schema. IMPORTANT: When adding connector actions (e.g., SQL, Service Bus, MSN Weather), use get_connector_swagger first to discover the correct action paths and schemas. For Consumption SKU with connector actions, use the 'connections' parameter to wire up API connections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesAzure subscription ID
resourceGroupNameYesResource group name
logicAppNameYesLogic App resource name (for Consumption, this becomes the new Logic App name)
definitionYesThe workflow definition JSON following the Logic Apps schema
locationNoAzure region (required for Consumption SKU, e.g., 'westus2', 'eastus')
workflowNameNoWorkflow name (required for Standard SKU)
kindNoWorkflow kind for Standard SKU (default: 'Stateful')
connectionsNoAPI connection references for Consumption SKU. Object mapping connection names used in the definition to their connection details. Example: {"office365": {"connectionName": "office365-test", "id": "/subscriptions/.../providers/Microsoft.Web/locations/.../managedApis/office365"}}
Behavior4/5

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

With no annotations, the description carries full burden. It explains the creation behavior for both SKUs, including required parameters and the need for a valid definition JSON. However, it does not mention potential side effects like overwriting existing resources or rate limits, which would improve transparency.

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 front-loaded with the main purpose, then efficiently covers SKU differentiation and important usage notes. Every sentence adds value, and there is no redundant information. It is well-structured for an agent to quickly parse.

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?

Given 8 parameters, full schema coverage, and no output schema, the description adequately covers all necessary context for correct invocation. It explains the two main usage paths and the critical prerequisite for connector actions, making it complete for an agent.

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%, but the description adds significant value beyond the schema: it explains SKU-specific requirements for location, workflowName, and LogicAppName, and provides a detailed example for the complex 'connections' parameter. This reduces ambiguity for the agent.

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 that the tool 'Create a new workflow' and distinguishes between Consumption and Standard SKU, specifying what resource is created. It provides a specific verb and resource, differentiating from sibling tools like clone_workflow or update_workflow.

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 states when to use for each SKU and provides a crucial prerequisite: use get_connector_swagger for connector actions. It also gives guidance on the 'connections' parameter for Consumption SKU. This helps the agent decide when to invoke this tool versus alternatives.

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