Skip to main content
Glama
ChrisChoTW

databricks-mcp

by ChrisChoTW

get_pipeline

Retrieve the current status of a Databricks pipeline to monitor its execution progress and identify any issues.

Instructions

Get pipeline status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pipeline_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the `get_pipeline` tool logic, interacting with the workspace client to retrieve pipeline details.
    @mcp.tool
    def get_pipeline(ctx: Context, pipeline_id: str) -> Dict[str, Any]:
        """Get pipeline status"""
        w = get_workspace_client()
        return w.pipelines.get(pipeline_id=pipeline_id).as_dict()
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get pipeline status' implies a read operation but lacks details on permissions, rate limits, error handling, or response format. 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.

Conciseness5/5

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

The description is extremely concise with just three words, front-loaded and free of unnecessary details. However, this brevity contributes to underspecification rather than effective communication.

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?

Given the presence of an output schema, the description doesn't need to explain return values, but it lacks essential context for a tool with no annotations and undocumented parameters. It fails to clarify the tool's role among siblings or provide basic usage guidance, making it incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no information about the 'pipeline_id' parameter. It doesn't explain what a pipeline ID is, its format, or where to obtain it, failing to compensate for the lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get pipeline status' restates the tool name 'get_pipeline' with minimal elaboration, making it tautological. While it specifies 'status' as the target, it doesn't distinguish this from sibling tools like 'list_pipelines' or 'list_pipeline_updates', leaving the scope unclear.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'list_pipelines' and 'list_pipeline_updates', the description fails to indicate whether this is for detailed status of a single pipeline or how it differs from other pipeline-related 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