Skip to main content
Glama

Create project

create_project

Create a project to keep a piece of work's assets and jobs together. Returns it with its id and slug.

kind says what the project is for (general, film, game, ads, app; default general). It picks the project's icon and which presets, workflows and docs are shown first, and never restricts what the project can run.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
nameYes
slugNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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 and openWorldHint=true. The description adds genuine context beyond them: the call returns the new object with id and slug, and `kind` only affects icon and which presets/workflows/docs are surfaced while never restricting execution. It says nothing about slug uniqueness/collision behavior or permissions, which matters for an open-world mutation.

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, front-loaded paragraphs: the operation and its result first, then the only non-obvious parameter. No filler, though the treatment of `kind` is more detailed than the unexplained `slug` warrants given relative risk.

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?

Return values are documented by the output schema, so omitting them is fine. However, for an open-world create tool with 0% schema coverage, the description should say what happens when `slug` is omitted or already taken, and whether name/slug are unique — details an agent needs to call it correctly once.

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?

Schema coverage is 0%, so the description must carry the load; it explains `kind` thoroughly (allowed values, default general, effects on icon/presets/docs, and that it is non-restrictive). It leaves `slug` (apparently optional, likely auto-derived from name) and `description` unexplained, and the "id and slug" return sentence does not clarify the slug parameter's purpose.

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+resource ("Create a project") and adds what the resource is for ("keep a piece of work's assets and jobs together"), plus what comes back (id and slug). It does not distinguish itself from siblings such as create_item or create_item's relation to projects, so it falls short of a 5.

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?

Usage is only implied by the phrase "keep a piece of work's assets and jobs together"; there is no explicit when-to-use vs. when-not, no mention of alternatives or prerequisites (e.g., whether a project must exist before create_item). Adequate for a straightforward create tool but with clear gaps.

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