Skip to main content
Glama
Sign In
SuperDev

SuperDev

by Xsxdot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Import pipeline template

import_pipeline_template

Import a pipeline template file into the local agent template library for reuse in DAG deploy pipelines.

Instructions

Import a pipeline template file into the local agent template library only.

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": {
      "path": "<path>"
    },
    "name": "import_pipeline_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
approval_tokenNo
debug_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full transparency burden. It only mentions 'local ... only' and does not disclose possible side effects such as overwriting existing templates, permission requirements, use of approval_token, or what happens on success/failure.

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?

The description is a single, front-loaded, 14-word sentence that clearly states the core action. It is concise and easy to parse, though it sacrifices depth in favor of brevity.

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 that this is a mutating operation with three parameters, no annotations, and no output schema, the description is far too sparse. It omits parameter semantics, return behavior, and operational context, making the tool difficult to invoke correctly.

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 offers no explanation of the three parameters: path, approval_token, and debug_session_id. The agent is left with no guidance on what values to provide or when they are relevant, which is critical for a tool with a required path and optional security/debug params.

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 the specific verb 'import' and clearly names the resource ('pipeline template file') and destination ('local agent template library only'). This distinguishes it from sibling tools such as deploy_project_pipeline or preview_pipeline_template, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The qualifiers 'local' and 'only' provide clear contextual boundaries, implying this tool is for local template import only and not for deployment or remote operations. However, it does not explicitly name alternative tools or elaborate on when to prefer this over related pipeline tools.

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