Skip to main content
Glama
Sign In
GreptimeDB MCP Server

GreptimeDB MCP Server

Official
by GreptimeTeam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_pipeline

Create a new data pipeline in GreptimeDB by providing a name and pipeline definition. Define processing logic for incoming data.

Instructions

Create a new pipeline in GreptimeDB.

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": {
      "name": "<name>",
      "pipeline": "<pipeline>"
    },
    "name": "create_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pipelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

C2.7/5.0
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. It states 'Create' implying mutation but lacks details on idempotency, side effects, permissions, error behavior (e.g., overwriting existing pipelines), or any constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

At one sentence, it is concise but sacrifices substance. It is front-loaded with the action and resource, but does not earn its brevity with added value beyond the obvious.

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 minimal description, lack of parameter details, no annotations, and existence of an output schema (unused), the description is incomplete. It fails to cover essential context for a tool with two required parameters.

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%, yet the description adds no information about the two required parameters 'name' and 'pipeline'. It does not explain what values are expected, defaults, or formats, leaving the agent uninformed.

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

Purpose5/5

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

The description uses a specific verb 'Create' and identifies the resource 'pipeline' in GreptimeDB, clearly distinguishing it from siblings like 'create_dashboard', 'delete_pipeline', and 'dryrun_pipeline'.

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 on when to use this tool versus alternatives such as 'dryrun_pipeline' for testing or 'list_pipelines' for inspection. There are no prerequisites, context, or use case hints.

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