Skip to main content
Glama
christianclaudio

snowflake-mcp-server

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Tasks Suspend Task

tasks_suspend_task
Idempotent

Pause an active scheduled task in Snowflake to stop scheduled runs. Provide the task name plus optional database and schema to suspend it without deleting its configuration.

Instructions

Suspend an active scheduled task.

Input Schema

NameRequiredDescriptionDefault
databaseNoQuote names that aren't all uppercase, exactly as list tools return them.
task_nameYesQuote names that aren't all uppercase, exactly as list tools return them.
schema_nameNoQuote names that aren't all uppercase, exactly as list tools return them.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • addedInput schema / properties / database / description
      Added value: +"Quote names that aren't all uppercase, exactly as list tools return them."
    • addedInput schema / properties / schema_name / description
      Added value: +"Quote names that aren't all uppercase, exactly as list tools return them."
    • addedInput schema / properties / task_name / description
      Added value: +"Quote names that aren't all uppercase, exactly as list tools return them."
  2. Addedv2.0.4

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=true, so the safety profile is covered. The description adds only the 'active' scoping hint and does not disclose what happens if the task is already suspended, what suspension does to in-flight runs, or required privileges.

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?

A single front-loaded sentence with no waste. It is efficient but arguably under-specified rather than optimally concise.

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

Completeness3/5

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

For a simple state-change tool with rich annotations and an output schema, the description is minimally sufficient. It leaves gaps around idempotent behavior on already-suspended tasks and any side effects, but the structured fields cover safety and returns.

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 coverage is 100%, so the schema already documents all three parameters including the naming/quoting convention. The description adds no parameter detail, which is acceptable at baseline when the schema fully carries the burden.

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?

The description states a specific verb and resource ('Suspend ... scheduled task') and the 'active' qualifier narrows the scope. It implicitly distinguishes from the sibling tasks_resume_task by naming the opposite operation, though it doesn't explicitly reference it.

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

Usage Guidelines3/5

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

The word 'active' implies the tool applies to active (running) tasks, giving partial usage context. However, there is no explicit when-to-use guidance, no mention of alternatives like tasks_resume_task, and no prerequisite information.

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

Deploy Server

Other Tools