Skip to main content
Glama
christianclaudio

snowflake-mcp-server

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Snowflake Get Current Context

snowflake_get_current_context
Read-only

Retrieve the active Snowflake session context—current user, role, warehouse, database, schema, and account—to verify environment and permissions before running queries or operations.

Instructions

Retrieve current active session context (current user, role, warehouse, database, schema, and account).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / title
      Removed value: -"snowflake_get_current_contextArguments"
    • removedOutput schema / title
      Removed value: -"snowflake_get_current_contextDictOutput"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only the set of context values returned, which the output schema likely already carries, so incremental behavioral value is modest.

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?

A single front-loaded sentence with no filler; every element (verb, scope, returned fields) earns its place. Nothing is repeated or padded.

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 parameterless, read-only introspection tool with an output schema and full annotation coverage, the description supplies everything needed to select and call it correctly. Nothing material is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool is 4. No argument syntax or defaults are relevant here.

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?

States a specific verb ('Retrieve') and resource ('current active session context') and enumerates the exact fields returned (user, role, warehouse, database, schema, account). No sibling tool covers session context, so the boundary is unambiguous.

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?

Usage is implied by the self-evident purpose, but the description never states when to call it or in what workflow (e.g., before running session-dependent queries). No alternatives are named, though none exist for this capability, so the omission is mild.

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