Skip to main content
Glama

Coline

Make a project

create_project

Makes a project: an outcome with its boards, people and crew. In a team workspace it can make a channel for it.

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": {
      "workspace": "<workspace>",
      "name": "<name>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
stateNo
crewIdsNo
outcomeNoThe outcome in one line.
boardIdsNo
peopleIdsNo
startDateNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
leadUserIdNo
targetDateNo
makeChannelNoMake a channel for it, with the project as a tab. Team workspaces only.

Output Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent creation call, and the description adds a genuinely useful side effect: it may create a channel with the project as a tab. It also reveals that boards, people and crew are attached at creation time, which is not obvious from the schema alone. It omits whether members are notified and what happens with invalid board/people IDs, which keeps it from a 5.

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?

Two short sentences, front-loaded with the core action, with no filler. The second sentence reads slightly as an afterthought but is still informative rather than redundant.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. However, for an 11-parameter creation tool the description leaves most parameters and the attachment semantics (what boards/people/crew must exist beforehand) unexplained, so it is only just adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 27% schema description coverage across 11 parameters, the description needs to carry more weight, but it only loosely gestures at boards, people, crew and the channel flag — all of which the schema already documents. The dates, state enum, leadUserId and workspace slug get no semantic elaboration at all.

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?

States a specific verb and resource ("Makes a project") and adds a definitional gloss — "an outcome with its boards, people and crew" — that tells the agent what a project contains. It does not contrast itself with siblings like create_taskboard or create_channel, so the agent must infer the boundary, but the purpose itself is unambiguous.

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?

The description offers no guidance on when to create a project versus using a sibling, nor any prerequisites such as required permissions or whether the caller must already be a member of the workspace. The only conditional statement — channel creation is "team workspaces only" — is a parameter constraint, not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources