Skip to main content
Glama

Add Project Tool

add_project

Creates a new team project with client, lead, repo, and optional template tasks. Use it after confirming the name and client; returns the project slug.

Instructions

Creates a new project (and its client, only with create_client when the person confirms the client is new), with an optional lead, repo, categories and description; optionally from a template that adds its standard tasks. For the team only: clients cannot create projects. Use it only when the person asks, after confirming the name, the client and the lead; to change an existing project use update_project. If projects with the same or a similar name exist it returns them instead (confirm_new creates the new one anyway); errors name the known clients or templates, or say the repo is already taken. Returns the project's slug (for a .cemainou file).

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

Input Schema

NameRequiredDescriptionDefault
leadNoWho leads it: "me" (default), a colleague's name or email.
nameYesThe project name, e.g. "Campanie Turism Local".
repoNoThe main git remote, if the project has a repo (git remote get-url origin).
clientNoThe client's name or slug; leave empty for an internal project.
templateNoOptional: the name of a project template (e.g. "Website"); its standard tasks are added on the project, free, with due dates from today. Only when the person names one.
categoriesNoOptional kinds of work, one or more (e.g. design and development).
confirm_newNotrue only after the person confirmed it is a new project, when a first call answered with similar projects.
descriptionNoOptional, one or two sentences.
create_clientNoCreate the client if it does not exist yet. Only after the person confirmed it is a new client (not a typo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it discloses the permission restriction, the side effect that a template adds standard tasks with due dates from today, the duplicate-name collision behavior that returns existing projects instead of creating, and what errors report.

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?

Core action, then usage constraints, then edge-case behavior and return value — well front-loaded and every clause carries information. It is dense with stacked parentheticals, which slows parsing slightly, but nothing is redundant.

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 9-parameter mutation tool with no annotations and no output schema, the description covers permissions, side effects, duplicate handling, error content, and the return value (project slug for a .cemainou file). An agent has everything needed to call it correctly.

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 100%, so baseline is 3; the description still adds non-obvious semantics — create_client may only be used after confirming the client is new (not a typo), and template should only be set when the person names one. It does not add much beyond the schema for lead/repo/categories.

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?

Opens with a specific verb+resource ('Creates a new project') and immediately scopes what gets created (optional lead, repo, categories, description, template tasks). It explicitly contrasts with update_project for changing existing projects, so an agent can separate it from the closest sibling.

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?

States explicit gating conditions: use only when the person asks, after confirming name/client/lead, team-only (clients cannot create projects), and route to update_project for changes. It also specifies the re-run flow with confirm_new after similar projects are returned.

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