Skip to main content
Glama

create_project

Create a Kanboard project with a required name. Optionally add description, identifier, owner, dates, and email. Returns the project ID.

Instructions

Create a new Kanboard project. Requires a name (1–255 chars). Optionally provide a description, short identifier, owner user id, start_date / end_date (ISO 8601 string or epoch seconds), and email. Returns { project_id } on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name (1–255 characters, required).
descriptionNoOptional project description.
identifierNoOptional short identifier (e.g. 'PRJ'). Must be unique across projects.
owner_idNoOptional numeric user id of the project owner.
start_dateNoOptional start date as ISO 8601 string or Unix epoch seconds (integer).
end_dateNoOptional end date as ISO 8601 string or Unix epoch seconds (integer).
emailNoOptional project notification email address.
Behavior4/5

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

Even without annotations, the description discloses the creation behavior, required name, optional fields, and return format. It does not cover permissions or potential side effects, but is adequate for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, concise and front-loaded with the core action, with no unnecessary information.

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

Completeness4/5

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

Given the lack of annotations and output schema, the description covers the basic behavior, parameters, and return value. It is complete enough for a simple creation tool.

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?

The description adds value by summarizing the purpose of parameters and noting the return format, which complements the 100% schema description coverage.

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 clearly states 'Create a new Kanboard project' with specific verb and resource. It distinguishes from siblings like update_project and list_projects by focusing on creation.

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 description implies usage by listing required and optional fields, but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ErnestoCorona/kanboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server