Skip to main content
Glama
christianclaudio

snowflake-mcp-server

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Snowflake Describe Password Policy

snowflake_describe_password_policy
Read-only

Retrieve password policy constraints such as minimum length, lockout time, history, and age to audit or verify Snowflake account security settings.

Instructions

Describe password policy constraints (min length, lockout time, history, age).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
databaseNo
policy_nameYes
schema_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / database / title
      Removed value: -"Database"
    • removedInput schema / properties / policy_name / title
      Removed value: -"Policy Name"
    • removedInput schema / properties / schema_name / title
      Removed value: -"Schema Name"
    • removedInput schema / title
      Removed value: -"snowflake_describe_password_policyArguments"
    • removedOutput schema / title
      Removed value: -"snowflake_describe_password_policyDictOutput"
  2. First observedv0.1.0

TDQS

C2.9/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 covered. The description adds some context by listing the constraint categories it returns, but does not disclose authentication needs, identifier qualification behavior, or other operational traits. This is a modest but not rich addition beyond the structured metadata.

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 a single front-loaded sentence with no filler. It immediately states the action and the relevant constraint categories, and every word earns its place.

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

Completeness2/5

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

Although an output schema and read-only annotations exist, the description is incomplete for an object-description tool with three parameters and 0% schema description coverage. It does not explain how to identify the target policy or how database and schema_name affect resolution, leaving important invocation details missing.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the three parameters. It never mentions policy_name, database, or schema_name, nor does it clarify that policy_name is required or how database/schema qualify the lookup. With three undocumented parameters, the description fails to compensate for the schema gap.

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: describe a Snowflake password policy. It also enumerates the kinds of constraints returned (min length, lockout time, history, age), which helps distinguish it from list_password_policies. It stops short of explicitly naming that sibling, so it is clear but not maximally differentiated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus list_password_policies or other policy-description tools. The implied usage is merely to inspect an existing policy, with no prerequisites, exclusions, or alternative paths mentioned.

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