snowflake-mcp-server

Snowflake Create Alert

snowflake_create_alert

Create a Snowflake alert by defining a schedule, condition SQL, and action SQL; set confirm=True for destructive actions.

Instructions

Create an alert with schedule, condition SQL, and action SQL. Destructive actions require confirm=True.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`comment`	No
`confirm`	No
`database`	No
`schedule`	Yes
`action_sql`	Yes
`alert_name`	Yes
`schema_name`	No
`condition_sql`	Yes
`warehouse_name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.2.0Oct 2, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / action_sql / title
```
Removed value: -"Action Sql"
```
- removedInput schema / properties / alert_name / title
```
Removed value: -"Alert Name"
```
- removedInput schema / properties / comment / title
```
Removed value: -"Comment"
```
- removedInput schema / properties / condition_sql / title
```
Removed value: -"Condition Sql"
```
- removedInput schema / properties / confirm / title
```
Removed value: -"Confirm"
```
- removedInput schema / properties / database / title
```
Removed value: -"Database"
```
- removedInput schema / properties / schedule / title
```
Removed value: -"Schedule"
```
- removedInput schema / properties / schema_name / title
```
Removed value: -"Schema Name"
```
- removedInput schema / properties / warehouse_name / title
```
Removed value: -"Warehouse Name"
```
- removedInput schema / title
```
Removed value: -"snowflake_create_alertArguments"
```
- removedOutput schema / title
```
Removed value: -"snowflake_create_alertDictOutput"
```

Changed1 schema field changedv1.1.5Sep 8, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "title": "Confirm",
+  "type": "boolean"
+}

First observedv0.1.0Aug 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds a genuine behavioral rule beyond the schema: confirm=True is required for destructive actions, which is valuable safety context the annotations do not convey. There is mild tension with destructiveHint=false (the tool's action SQL can destroy data), but calling this a full contradiction would be harsh since the confirm guard exists precisely for that case.

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?

Two tight sentences, front-loaded with the purpose before the safety rule, with no filler. It is efficient, though the brevity is partly under-specification rather than economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but for a 9-parameter write tool with a required warehouse, no defaults documented, and no context fallback described, the definition is thin. Notably missing: Snowflake creates alerts suspended (requiring resume_alert), and behavior when the alert already exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description carries the full burden — and it only names four of them (schedule, condition_sql, action_sql, confirm). alert_name, warehouse_name, database, schema_name and comment are left completely unexplained, including whether database/schema fall back to the session context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create an alert') and names the three defining parameters (schedule, condition SQL, action SQL) that distinguish the operation. However, it does not distinguish itself from siblings like snowflake_create_task or snowflake_create_pipe, which have near-identical shapes, so an agent gets no explicit routing help.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is 'Destructive actions require confirm=True', which hints at a prerequisite but never says when to prefer this tool over snowflake_create_task, nor what environmental conditions (warehouse, database/schema context) must hold first. No alternatives, no when-not-to-use.

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

Deploy Server