Skip to main content
Glama

create_project

Create a project with a unique key, a title, and an optional description. The key is stored uppercase, prefixes every task key, and must not be already taken.

Instructions

Creates a project with a key, a title and a description. Only a main token creates projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesKey of the new project: a Latin letter followed by 1–15 Latin letters or digits (`invalid_project_key` otherwise). It is stored upper-case, never changes and prefixes the key of every task of the project. A key already taken, in any case, is refused with `project_key_taken`
titleYesProject title
descriptionNoShort "what this is", up to 320 characters after trimming; a longer one is refused with `project_description_too_long`. It rides in the card of every task of the project
idempotency_keyNoRetry key chosen by the caller, e.g. a UUID. A repeat with the same key and the same arguments returns the first result and creates nothing; the same key with other arguments is refused with `idempotency_key_reused`. A key is bound to the caller's token and kept for 24 hours

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.2

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already indicate this is a write operation (readOnlyHint=false). The description adds a useful non-obvious behavioral constraint: only a `main` token may create projects. This goes beyond what the annotations provide.

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 compact with two short sentences and no filler. The first sentence is somewhat redundant with the tool name and schema, but the second sentence carries important auth context, so the overall structure is reasonably efficient.

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 simple create tool with a rich input schema and an output schema, the description covers the core operation and the critical auth constraint. However, it lacks routing guidance relative to sibling tools and does not describe any side effects beyond the annotations.

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 description coverage is 100%, so the input schema already documents all four parameters in detail. The description merely echoes key, title, and description and adds no additional semantic value beyond what the schema provides.

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 states a specific verb and resource: 'Creates a project', and names the main attributes (key, title, description). It is clear but does not explicitly distinguish itself from sibling tools such as update_project or create_task.

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 given on when to use this tool versus alternatives. The note that only a `main` token creates projects is an authorization precondition, not a routing guideline for choosing create_project over create_task or update_project.

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