You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/marketplace/platform-supported-content/modules/snowflake/snowflake-mcp-agent.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,10 @@ For Method 2, you also need the following:
50
50
51
51
## Example Scenario
52
52
53
+
{{% alert color="info" %}}
54
+
The following examples demonstrate the integration pattern. For production use, consider adding stronger error handling, security, retries, response validation, and logging.
55
+
{{% /alert %}}
56
+
53
57
The examples in this article use a Mendix MCP tool named *RetrieveNumberOfTicketsInStatus*. This tool is exposed by a Mendix microflow and accepts the following input:
54
58
55
59
| Parameter | Type | Description |
@@ -64,8 +68,6 @@ The microflow returns the number of tickets for the given status. In this exampl
64
68
| Closed | 128 |
65
69
| In Progress | 19 |
66
70
67
-
If a value other than the supported statuses is provided, the microflow throws an exception.
68
-
69
71
A user interacting with the Cortex Agent can ask a question such as, *How many tickets are open?*
70
72
71
73
The agent invokes the appropriate tool and returns the result.
@@ -351,7 +353,7 @@ To configure your app for method 2, perform the following steps:
351
353
352
354
Keep your client secret confidential. Do not include it in shared documentation, code, or version control systems.
353
355
354
-
2. Create a Snowflake API integration that configures OAuth 2.0 access to the Mendix MCP endpoint:
356
+
2. Create a Snowflake API integration to configure OAuth 2.0 access to the Mendix MCP endpoint:
355
357
356
358
```text
357
359
USE ROLE ACCOUNTADMIN;
@@ -513,4 +515,4 @@ The agent does not invoke the expected tool.
513
515
514
516
##### Solution
515
517
516
-
Verify that the Mendix MCP server exposes the tool correctly and that the MCP connector is in a connected state in the agent session. If the connector shows as disconnected, click **Connect** and complete the authorization flow.
518
+
Verify that the Mendix MCP server exposes the tool correctly and that the MCP connector is in a connected state in the agent session. If the connector shows as disconnected, click **Connect** and complete the authorization flow.
0 commit comments