Skip to main content
Glama
ChrisChoTW

databricks-mcp

by ChrisChoTW

get_grants

View permissions for Databricks objects like tables, schemas, and catalogs by specifying the object type and full name to check access rights.

Instructions

View object permissions (SHOW GRANTS)

Args: securable_type: Object type (TABLE, SCHEMA, CATALOG, VOLUME, etc.) full_name: Full object name (catalog.schema.table format)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
securable_typeYes
full_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_grants tool handler executes the 'SHOW GRANTS' SQL command to retrieve permissions for a specified Unity Catalog object. It includes input validation for the securable type and the object name components.
    def get_grants(ctx: Context, securable_type: str, full_name: str) -> List[Dict[str, Any]]:
        """
        View object permissions (SHOW GRANTS)
    
        Args:
            securable_type: Object type (TABLE, SCHEMA, CATALOG, VOLUME, etc.)
            full_name: Full object name (catalog.schema.table format)
        """
        validated_type = validate_securable_type(securable_type)
        # Validate and quote full_name parts
        parts = full_name.split(".")
        quoted_parts = []
        for part in parts:
            validate_identifier(part, "full_name component")
            quoted_parts.append(quote_identifier(part))
        quoted_full_name = ".".join(quoted_parts)
        return execute_sql(ctx, f"SHOW GRANTS ON {validated_type} {quoted_full_name}")
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states 'View object permissions' which implies a read-only operation, but doesn't disclose authentication needs, rate limits, error conditions, or what the output contains beyond permissions. This is inadequate for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence adds value, and it's appropriately brief for a tool with only two parameters. Minor improvement could be made by integrating the parameter details more seamlessly.

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

Completeness3/5

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

Given the tool has an output schema (which handles return values) and only two parameters, the description covers the basics but has gaps. It explains parameters well but lacks behavioral context and usage guidelines. For a permissions-viewing tool with no annotations, more detail about what 'permissions' includes would be helpful.

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 description adds meaningful context beyond the input schema. While schema description coverage is 0%, the description explains that securable_type includes values like 'TABLE, SCHEMA, CATALOG, VOLUME, etc.' and that full_name uses 'catalog.schema.table format'. This provides essential semantic understanding that the raw schema lacks.

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 clearly states the tool's purpose: 'View object permissions' with the specific action 'SHOW GRANTS'. It identifies the resource as 'object permissions' but doesn't explicitly differentiate from sibling tools like get_table_schema or get_table_detail, which focus on different aspects of database objects.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or compare it to sibling tools like get_table_detail or list_tables, leaving the agent without usage direction.

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/ChrisChoTW/databricks-mcp'

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