Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_pipeline

Fetches a specific pipeline's full JSON configuration by name, covering source, data quality, transformation, preprocessor, and destination sections.

Instructions

Get a specific pipeline configuration by name. Returns the full JSON config including source, dataQuality, transformation, preprocessor, and destination sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipeline": "<pipeline>"
    },
    "name": "get_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pipelineYesPipeline name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose the return shape by enumerating source, dataQuality, transformation, preprocessor, and destination. It omits behavior for a missing pipeline name, permission requirements, and — importantly given a get_pipeline_version sibling — whether this returns the current or latest version.

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 short sentences, front-loaded with the operation and followed by the return contents. No filler or redundant restatement of the tool name.

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?

For a simple single-parameter getter this covers purpose and return structure adequately, so an agent can call it correctly. The remaining gap is versioning semantics, which matter because get_pipeline_version exists as a sibling.

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

Parameters3/5

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

Schema coverage is 100% for the single 'pipeline' parameter, so the baseline applies. The phrase 'by name' adds a small amount of meaning, clarifying that lookup is by name rather than ID, but no format or case-sensitivity detail is given.

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?

States a specific verb and resource ('Get a specific pipeline configuration by name') and names the exact configuration sections returned. The word 'configuration' implicitly separates it from siblings like get_pipeline_status and get_pipeline_result, but no sibling is explicitly named or excluded.

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?

There is no when-to-use guidance, no prerequisites, and no statement of alternatives. An agent must infer that this is the right tool for reading a pipeline's definition rather than its status, result, or a specific version.

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

Deploy Server

Other Tools