snowflake-mcp-server

Tables Create Table

tables_create_table

Create a Snowflake table using specified column SQL definitions, with optional database, schema, and if-not-exists handling.

Instructions

Create a table in Snowflake with specified column definitions SQL.

Input Schema

Name	Required	Description
`database`	No	Quote names that aren't all uppercase, exactly as list tools return them.
`table_name`	Yes	Quote names that aren't all uppercase, exactly as list tools return them.
`columns_sql`	Yes
`schema_name`	No	Quote names that aren't all uppercase, exactly as list tools return them.
`if_not_exists`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.0.0Oct 30, 2026

addedInput schema / properties / database / description

Added value: +"Quote names that aren't all uppercase, exactly as list tools return them."

addedInput schema / properties / schema_name / description

Added value: +"Quote names that aren't all uppercase, exactly as list tools return them."

addedInput schema / properties / table_name / description

Added value: +"Quote names that aren't all uppercase, exactly as list tools return them."

Addedv2.0.4Oct 17, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The description merely states the action. Since the annotations already specify the mutation nature (readOnlyHint: false, destructiveHint: false), the description adds minimal unique behavioral context beyond restating the name.

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 highly concise, consisting of a single sentence that front-loads the primary action and target resource efficiently.

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?

As a high-privilege mutation tool for creating infrastructure objects, the description is incomplete. It does not warn about potential risks of duplicate names, or constraints on the required SQL syntax, despite annotations providing basic safety hints.

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 description mentions 'specified column definitions SQL,' which provides context for the columns_sql parameter. However, given that schema description coverage is only 60%, the description does not do enough to compensate for the missing definitions of the other 40% of parameters.

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?

Thedescription clearly identifies the action ('Create a table') and the environment ('Snowflake'). It is specific and directly relates to the tool's function.

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

Usage Guidelines1/5

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

The description offers absolutely no guidance on when to use this tool versus alternatives (e.g., tables_clone_table or tables_describe_table). It lacks any contextual exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server