Skip to main content
Glama

project_create

Create a new Work Plan project and optionally seed tasks from a local Markdown plan, folder subdirectories, or GitHub issue URL to start structured project tracking.

Instructions

Create a new Work Plan project and optionally seed tasks from a local Markdown plan, folder subdirectories, or GitHub issue URL.

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": "project_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoWhether to auto-seed tasks from source_ref (default true).
titleNoProject title (optional if seeded from Markdown, folder, or GitHub URL).
kp_modeNoKnowledge Pack mode (auto, okf, markdown, disabled).
kp_pathNoOptional path to Knowledge Pack (OKF bundle directory/index.md or single Markdown file).
source_refNoOptional path to PLAN.md/SPEC.md, local folder, or GitHub issue URL.
workspace_dirNoLocal workspace directory path.

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?

No annotations are provided, so the description carries the full burden. It does disclose a meaningful side effect beyond the schema — that creation can also generate tasks from external sources — but says nothing about permissions, idempotency, failure modes, or what happens to existing state.

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?

A single front-loaded sentence with no filler; the primary action comes first and the optional seeding is subordinated. Slightly compressed to the point that the seeding mechanics are underspecified, but nothing is wasted.

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

Completeness3/5

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

For a six-parameter creation tool with no annotations and no output schema, the description is adequate but thin. It does not explain how title, source_ref, seed, and kp_mode interact, nor what the caller gets back, leaving the agent to reason from the schema alone.

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%, so the schema already documents all six parameters including defaults and the enum. The description restates the source types for source_ref but adds no meaning for kp_mode, kp_path, or workspace_dir, so the baseline of 3 applies.

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?

The description names a specific verb and resource ("Create a new Work Plan project") and adds the distinguishing capability of seeding tasks from Markdown, folders, or GitHub issues. It is clear what the tool does, though it does not explicitly contrast itself with the sibling ui_create_project.

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

Usage Guidelines3/5

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

Usage is implied by the seeding sources mentioned, but there is no explicit statement of when to prefer this over ui_create_project or when seeding should be skipped. An agent can infer intent but must guess about alternatives.

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