Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

snowflake_sessions

List active multiplexed Snowflake session pools as YAML, showing per-pool account/user, live/max sessions, and query counts for monitoring daemon activity.

Instructions

List the omni-dev daemon's active multiplexed Snowflake sessions as YAML (per-pool account/user, live/max sessions, query counts). Read-only. Mirrors omni-dev snowflake sessions. Requires a running daemon.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "snowflake_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
socketNoControl-socket path override. Defaults to the per-user runtime location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `snowflake_sessions` tool."
    • removedInput schema / title
      Removed value: -"SnowflakeSessionsParams"
  2. Addedv0.32.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool is read-only and requires a running daemon, but does not mention error behaviors, rate limits, or what happens if the daemon is not running. This is adequate but not thorough.

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 extremely concise, using a few short sentences to convey purpose, output format, read-only nature, command alias, and prerequisite. Every sentence is necessary and no words are wasted.

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 low complexity (1 optional parameter, no output schema, no annotations), the description covers the essential aspects: what it does, output format, read-only attribute, and the daemon requirement. It is largely complete, though it could mention handling of empty results or errors.

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?

The input schema covers the single parameter 'socket' with a description, achieving 100% coverage. The description does not add additional parameter information beyond the schema, so baseline score of 3 is appropriate.

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 lists active multiplexed Snowflake sessions, specifies the output format (YAML) and content (per-pool account/user, live/max sessions, query counts), and distinguishes it from siblings like snowflake_query or snowflake_disconnect by noting it is read-only and mirrors a specific command.

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 implies usage by stating it lists sessions and requires a running daemon, but it does not explicitly say when to use vs alternatives or when not to use it. However, the context is clear enough given sibling tool names.

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