Skip to main content
Glama

ui_create_project

Creates a new engineering project from the UI modal using a title, seed, source reference, and workspace directory to set up project management.

Instructions

App-only: create a new project from the UI modal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ui_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
titleNo
source_refNo
workspace_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does convey one useful constraint, that this is an app-only UI-modal path, but it says nothing about what state is created, what happens with an existing project, whether the caller must be in a modal context, or what the response contains.

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?

A single short sentence with the scoping qualifier front-loaded and no wasted words. It is efficient, though the brevity is achieved through under-specification rather than tight writing.

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

Completeness2/5

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

This is a mutation tool with no annotations, no output schema, and four entirely undocumented parameters. Given that an agent must guess the meaning of seed and source_ref in order to call it correctly, the definition falls well short of what the complexity requires.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (seed, title, source_ref, workspace_dir), and the description explains none of them. An agent learns nothing about what seed controls or how source_ref and workspace_dir interact when creating the project.

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?

The description names a specific verb and resource ("create a new project") and adds the qualifier "App-only … from the UI modal", which hints at the boundary with the non-UI sibling project_create. It does not explicitly name or contrast with that sibling, so the differentiation is implied rather than stated.

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?

"App-only" and "from the UI modal" imply the calling context (in-app UI flows rather than programmatic project creation), which is a real usage constraint. However, there is no explicit when-to-use versus project_create, no prerequisites, and no statement of when this should not be used.

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