Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

snowflake_disconnect

Evict an active Snowflake session by account and user, returning whether the session was actually removed.

Instructions

Disconnect (evict) one multiplexed Snowflake session identified by its account and user. Mirrors omni-dev snowflake disconnect. Returns whether a session was actually evicted. Requires a running daemon.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "user": "<user>"
    },
    "name": "snowflake_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUser of the session to evict.
socketNoControl-socket path override. Defaults to the per-user runtime location.
accountYesAccount of the session to evict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.40.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `snowflake_disconnect` tool."
    • removedInput schema / title
      Removed value: -"SnowflakeDisconnectParams"
  4. Addedv0.32.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It adds useful behavioral details: the tool returns whether a session was actually evicted, and it requires a running daemon. The term 'evict' also discloses the destructive nature of the operation. This goes beyond simply restating the action.

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 composed of four short, information-dense sentences: action and target, CLI mirror, return value, and prerequisite. Every sentence adds unique value with no redundancy.

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?

For a simple disconnect tool with no output schema and only three parameters, the description is complete: it explains the purpose, the required identifiers, the return value, and a key prerequisite. It also distinguishes itself from sibling Snowflake tools.

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 description coverage is 100% and the parameter descriptions in the schema are already clear (e.g., 'User of the session to evict', 'Control-socket path override'). The description adds only minor reinforcement by stating the session is identified by `account` and `user`, but does not provide additional meaning beyond the schema.

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 action ('Disconnect (evict)') and the specific resource ('one multiplexed Snowflake session identified by its `account` and `user`'). It differentiates from sibling tools like snowflake_sessions by specifying the eviction action and the required identifying fields.

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 provides clear context for when to use the tool: to disconnect a specific session using account and user. It also gives a prerequisite ('Requires a running daemon') and references the CLI command (`omni-dev snowflake disconnect`), but does not explicitly mention alternatives or when-not-to-use scenarios.

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