Skip to main content
Glama
laveeshb

logicapps-mcp

by laveeshb

create_connection

Creates API connections for managed connectors such as azureblob or sql. For OAuth-based connectors, generates a consent link for browser authorization; for parameter-based, supplies connection parameters.

Instructions

Create a new API connection for a managed connector (e.g., azureblob, sql, servicebus, office365). For OAuth-based connectors (like azureblob with OAuth, office365), returns a consent link that must be opened in a browser to authorize. For parameter-based connectors (like SQL with connection string), provide the parameters directly. Common OAuth connectors: azureblob, office365, outlook, onedrive, sharepoint, dynamicscrm. Common parameter connectors: sql (server, database, username, password), servicebus (connectionString).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesAzure subscription ID
resourceGroupNameYesResource group name
connectionNameYesName for the new connection (e.g., 'azureblob-1', 'my-sql-connection')
connectorNameYesManaged connector name (e.g., 'azureblob', 'sql', 'servicebus', 'office365')
locationYesAzure region (e.g., 'westus2', 'eastus'). Should match Logic App region.
displayNameNoFriendly display name for the connection (optional, defaults to connectionName)
parameterValuesNoConnection parameters for non-OAuth connectors. Examples: SQL: {server, database, username, password, encryptConnection}. ServiceBus: {connectionString}. Leave empty for OAuth connectors.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: OAuth connectors return a consent link that must be opened in a browser, and parameter-based connectors require direct parameters. It does not cover idempotency or error handling, but the disclosed behavior is sufficient for most use cases.

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 a single paragraph of 5-6 sentences, front-loaded with purpose, then logically covering OAuth vs parameter distinction and examples. No unnecessary words, well-structured.

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 complexity (7 params, no output schema, no annotations), the description covers the main behavioral and parameter aspects. It explains the consent link for OAuth and lists common connectors. It could mention idempotency or result handling after consent, but overall it is reasonably complete.

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 baseline is 3. The description adds value by categorizing parameters for OAuth vs parameter-based connectors, providing specific examples (SQL: server, database, username, password; ServiceBus: connectionString). This goes beyond the schema descriptions.

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 creates a new API connection for a managed connector, with specific examples (azureblob, sql, servicebus, office365). It distinguishes from sibling tools like create_workflow (different resource) and test_connection (testing vs creation).

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?

The description explains when to use the tool (creating connections) and provides detailed guidance on OAuth vs parameter-based connectors, including specific parameter examples. However, it does not explicitly state when not to use it or compare to alternatives like test_connection.

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