Skip to main content
Glama
dolphin-mcp-pilot

dolphin-mcp-pilot

ds_create_project

Create a new DolphinScheduler project owned by the current user, with a unique name and optional description. Use it to set up a workspace for workflows; check existing projects first to avoid name conflicts.

Instructions

Create a new project owned by the current user.

Fails if a project with the same name already exists; check with ds_list_projects first. Use ds_rename_project to change it later.

Args: name: Project name, unique in DolphinScheduler description: Optional description

Returns: {"id": int, "code": int, "name": str}; other tools take the project by name.

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>"
    },
    "name": "ds_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the uniqueness failure mode, that the project is owned by the current user, and that other tools address the project by name rather than id. Not covered: what permissions are needed to create, or whether any quota/namespace constraints apply.

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?

Purpose, failure condition and alternative are front-loaded in the first two sentences, with the Args/Returns block scoped to genuinely additive information. Slightly padded by restating parameter titles that the schema already names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description supplies the return shape ({id, code, name}), the key usage note that other tools take the project by name, and the duplicate-name hazard. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 0%, so the description must compensate, and it does for the key parameter by stating the name must be unique in DolphinScheduler and that description is optional. It adds no format, length, or character-set constraints for either field.

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?

States a specific verb and resource ('Create a new project') plus scope ('owned by the current user'), which immediately separates it from ds_rename_project, ds_list_projects and ds_delete_project without needing to open a schema.

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 says to check ds_list_projects first because creation fails on a duplicate name, and names ds_rename_project as the tool for later changes. Both the pre-condition and the follow-up alternative are stated rather than implied.

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