Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

update_tag

Update the masking configuration for an existing Snowflake tag. Provide tag group ID, database ID, and friendly name; optionally modify masking type, custom role, or data type list.

Instructions

Update an existing tag connection's masking configuration.

SNOWFLAKE ONLY. Databricks tags are not ALTR-managed objects, so there is no Databricks tag configuration to update — change Databricks masking by editing the policy or its rules instead.

Use get_tags to find the tag_group_id of the tag you want to update. To connect a new tag, use connect_tag instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tag_group_idYesTag group identifier from `get_tags`.
database_idYesNumeric ALTR database ID (from `get_database_id`).
friendly_nameYesDisplay name for the tag in ALTR.
protection_typeNoMasking type — "governed", "governed-pushdown", "tokenized-vault", or "encryption-fpe".governed
custom_role_provider_enabledNoEnable custom role provider UDF.
mask_data_type_listNoOptional list of data types to mask.
encryption_fpe_optionsNoOptional FPE config dict with 'alphabet' ("numeric"|"alphabetic"|"alphanumeric"), 'is_padded' (bool), 'key_name' (str), and 'tweak_name' (str).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, description carries full burden. It states the operation is an update (implying mutation) and Snowflake-only constraint. However, it lacks details on idempotency, permissions, error states, or side effects beyond the basic operation.

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?

Two concise paragraphs: first states purpose and Snowflake-only restriction, second provides usage hint and sibling tool. Front-loaded, no redundant words.

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?

Covers Snowflake-only constraint, prerequisites, and sibling differentiation. Missing explicit mention of success/response, but output schema exists (per context) so not required. Adequately complete given tool complexity.

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?

Schema coverage is 100% so baseline 3. Description adds value by guiding use of get_tags for tag_group_id and framing parameters as masking configuration. This extra context elevates the score to 4.

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 updates a tag connection's masking configuration, specifies the resource (tag connection), and distinguishes it from connect_tag (for new tags). It also mentions Snowflake-only scope.

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

Usage Guidelines5/5

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

Explicitly states Snowflake-only usage, explains Databricks tags are not supported and directs to policy/rules instead. Provides prerequisite (use get_tags) and links to connect_tag for new tags, giving clear when-to-use and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/altrsoftware/altr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server