governance_get_current_contextRetrieve current active session context—user, role, warehouse, database, schema, account—to confirm governance scope before Snowflake operations.
Retrieve current active session context (current user, role, warehouse, database, schema, and account).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, openWorld, and an output schema exists. The description confirms it reads session state but adds no behavioral context beyond the annotations, such as whether it requires a live session or reflects server-side defaults.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single well-formed sentence that front-loads the verb and resource and lists the returned fields with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-param read tool with full annotations and an output schema, the definition covers what is needed. The only minor gap is the absence of any note on when in a workflow to call it versus sibling listing tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so baseline is 4. Schema coverage is 100% with an empty object, leaving nothing for the description to clarify.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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'), then enumerates the exact fields returned (user, role, warehouse, database, schema, account). An agent can immediately distinguish this from schema/role listing tools like governance_list_roles or governance_describe_user.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The word 'current' implies this is a session-state read used before acting on the active context, but no explicit when-to-use or when-not-to-use guidance or named alternative is given. Usage is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.