Skip to main content
Glama
ChrisChoTW

databricks-mcp

by ChrisChoTW

list_volumes

Retrieve Unity Catalog volumes from Databricks to manage and organize data storage. Specify catalog and schema to filter results.

Instructions

List Unity Catalog Volumes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalogYes
schemaYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `list_volumes` uses `@mcp.tool` for registration and executes a SQL query to list Unity Catalog Volumes.
    @mcp.tool
    def list_volumes(ctx: Context, catalog: str, schema: str) -> List[Dict[str, Any]]:
        """List Unity Catalog Volumes"""
        cat = safe_identifier(catalog, "catalog")
        sch = safe_identifier(schema, "schema")
        return execute_sql(ctx, f"SHOW VOLUMES IN {cat}.{sch}")
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'List' implies a read-only operation, but the description doesn't disclose any behavioral traits - no information about authentication requirements, rate limits, pagination, or what happens when invalid catalog/schema parameters are provided. It's minimal but not misleading.

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 extremely concise - a single phrase with zero wasted words. It's front-loaded with the essential information (list Unity Catalog Volumes) and doesn't include any unnecessary elaboration.

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 that an output schema exists (which should document return values), the description's minimalism is somewhat acceptable. However, for a tool with 2 required parameters and 0% schema description coverage, the description should provide at least basic parameter context. It's borderline adequate but leaves significant gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema provides no parameter documentation. The description adds no information about the two required parameters (catalog and schema) - it doesn't explain what they represent, their format, or their relationship. The description fails to compensate for the complete lack of schema documentation.

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 verb ('List') and resource ('Unity Catalog Volumes'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_catalogs', 'list_schemas', or 'list_tables', which all follow the same 'list_[resource]' pattern for Unity Catalog entities.

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 about when to use this tool versus alternatives. With multiple list tools available (list_catalogs, list_schemas, list_tables), the description doesn't explain that this specifically lists volumes within a catalog and schema, nor does it mention prerequisites or relationships to other tools.

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