Skip to main content
Glama

Create a project

create_project
DestructiveIdempotent

Creates an empty static project with a stable address in the selected Personal space or workspace. Rotation at the Personal project limit requires explicit approval of the named project. project_destination_required identifies an unresolved destination.

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>",
      "label": "<label>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
labelYes
domainNo
descriptionNo
spa_fallbackNo
workspace_idNoNew project destination already chosen by the user: null for Personal, or an exact workspace ID. Omit if undecided; the server asks when shared destinations exist, and uses Personal automatically only when it is the only destination. Never fill a default on the user’s behalf.
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
confirm_rotation_project_idNoExact stable project ID. Resolve it first. Never invent an update target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description does not explain why project creation is destructive or what makes it idempotent. It does add useful behavior beyond the annotations: the Personal-project-limit rotation gate with its approval requirement, and the named unresolved-destination condition. That is real added context, but the destruction and idempotency story remains undisclosed.

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

Conciseness3/5

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

Three sentence fragments, front-loaded with the core action, which is good. However 'Rotation at the Personal project limit requires explicit approval of the named project' is jargon-heavy and never defines 'rotation', and 'project_destination_required identifies an unresolved destination' reads like a bare error token without saying it is an error condition.

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?

Covers the two trickiest flows (limit rotation, unresolved destination), which suits a create tool with no output schema. But for a mutation with destructiveHint and 8 parameters at 38% schema coverage, an agent still gets no statement about what is created or returned, nor about the domain and spa_fallback settings.

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 only 38%, so the description must compensate, and it partially does by tying 'explicit approval of the named project' to confirm_rotation_project_id and 'selected ... space or workspace' to workspace_id. It says nothing about name, label, domain, description, spa_fallback, or idempotency_key reuse, leaving more than half the surface to the schema.

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 ('Creates an empty static project') plus the scope of placement ('Personal space or workspace') and the outcome ('stable address'). The word 'static' implicitly separates it from create_dynamic_project, but that sibling is never named, so an agent must infer the distinction.

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?

Provides conditional guidance for two edge cases: exceeding the Personal project limit requires explicit approval of the named project, and 'project_destination_required' signals an unresolved destination. It gives no explicit guidance on when to choose this over create_dynamic_project, nor on how destination selection should proceed; that instruction lives only in the workspace_id schema description.

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