Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_pipelines

Retrieves all registered pipeline configurations, showing existing source schemas, AI transformations, and destinations so users can assess available data flows before making data-related requests.

Instructions

List all registered pipeline configurations. Each pipeline defines a complete data processing flow: source format and schema, AI-powered data quality and transformations, and destination (database, message queue, or vector store). CALL THIS FIRST on any data-related user request — before suggesting external sources, before asking scope questions. The user almost always cares more about what's already in their Datris environment than about a generic options menu.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pipelines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'List' implies read-only, and the description usefully explains the shape of what a pipeline record represents, but it says nothing about result volume, pagination, permissions, or whether an empty environment returns an empty list versus an error. Adequate but with real gaps for a no-annotation tool.

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?

Front-loaded with the verb and resource, then the behavioral explanation, then the priority directive — a sensible ordering. The closing sentence ('The user almost always cares more about what's already in their Datris environment...') is a soft marketing rationale rather than operational instruction, but it does reinforce the routing rule.

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 zero-parameter listing tool with no output schema, the definition covers purpose, record contents, and usage priority. It lacks only return-size or pagination behavior, which is a minor omission given the tool's simplicity.

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 tool takes zero parameters, so there is no parameter semantics for the description to add and the baseline of 4 applies. Nothing here misleads or omits anything about inputs.

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 ('List all registered pipeline configurations') and goes further to define what a pipeline configuration contains: source format/schema, transformations, and destination. That definitional context makes it distinguishable from generic listing tools. It does not, however, differentiate itself from the closely-named sibling list_pipeline_versions, which an agent could easily confuse with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'CALL THIS FIRST on any data-related user request — before suggesting external sources, before asking scope questions,' which gives both a trigger condition and a precedence ordering against other actions. This is unusually strong routing guidance for an agent choosing among siblings.

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