Skip to main content
Glama
ChrisChoTW

databricks-mcp

by ChrisChoTW

get_table_history

View change history for Delta tables to track modifications, analyze version changes, and monitor table evolution over time.

Instructions

View Delta table change history (DESCRIBE HISTORY)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalogYes
schemaYes
tableYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_table_history tool is defined and registered using the @mcp.tool decorator in tools/delta.py. It executes a SQL DESCRIBE HISTORY statement to fetch the table's change history.
    @mcp.tool
    def get_table_history(ctx: Context, catalog: str, schema: str, table: str, limit: int = 10) -> List[Dict[str, Any]]:
        """View Delta table change history (DESCRIBE HISTORY)"""
        cat = safe_identifier(catalog, "catalog")
        sch = safe_identifier(schema, "schema")
        tbl = safe_identifier(table, "table")
        return execute_sql(ctx, f"DESCRIBE HISTORY {cat}.{sch}.{tbl} LIMIT {limit}")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the action ('View') but doesn't specify whether this is read-only, if it requires specific permissions, what the output format is, or any rate limits. The parenthetical '(DESCRIBE HISTORY)' adds some context but is vague.

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 with a single, front-loaded sentence and a brief parenthetical. There is no wasted text, making it easy to parse quickly.

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 there is an output schema (which handles return values), the description's minimalism is somewhat acceptable. However, for a tool with 4 parameters (3 required) and no annotations, it lacks details on behavior, usage, and parameter meanings, making it incomplete for safe and effective use.

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 description must compensate for undocumented parameters. It doesn't explain what 'catalog', 'schema', 'table', or 'limit' mean, their expected formats, or how they relate to Delta tables. The description adds no parameter semantics beyond the schema.

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 action ('View Delta table change history') and specifies the resource type ('Delta table'), which distinguishes it from siblings like get_table_detail or get_table_schema. However, it doesn't explicitly differentiate from get_table_lineage or other history-related tools, keeping it at a 4 rather than a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like get_table_detail or get_table_lineage, nor does it mention prerequisites or context for invoking it. It simply restates the purpose without usage instructions.

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