Skip to main content
Glama

Create project

create_project

Create a new project for the connected user when requested. Does not invite users. An optional description is placed in the initial project document. Preserve requestId on retries.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name requested by the user. For updates, omit to keep the current name.
requestIdYesA unique UUID for this intended action. Reuse it unchanged when retrying the same action.
descriptionNoOptional text for the new task or the initial project document.

Output Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description usefully adds two things beyond that: the side effect of seeding an initial project document with the optional description, and the retry contract of reusing requestId. It still says nothing about permission requirements, duplicate-name behavior, or what a failure looks like.

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?

Four short sentences, front-loaded with the action and immediately followed by the negative scope and the retry rule; nothing is buried. The phrase "when requested" is near-redundant and earns little, keeping it from a 5.

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?

An output schema exists, so return values need no explanation, and the annotations carry the safety profile. With those covered, the description supplies the remaining essentials an agent needs: scope boundary, document side effect, and retry idempotency. Only permission/auth expectations and duplicate-handling are absent.

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 all three parameters are already documented, including the requestId retry semantics and the name length constraints. The description only adds that the description text lands in the initial project document, which is a small clarification rather than substantive new parameter meaning. Baseline 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?

"Create a new project for the connected user" gives a specific verb and resource, and "Does not invite users" bounds the scope so an agent won't expect member provisioning. It stops short of naming any sibling (e.g. create_task/create_doc) as the alternative for related work, so differentiation is partial rather than explicit.

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?

"when requested" implies user-initiated creation but gives no concrete trigger conditions, prerequisites, or exclusions beyond the invite note. There is no routing guidance toward list_projects (to check for existing projects) or toward the other create_* tools, leaving the agent to infer the choice.

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.