Skip to main content
Glama

Create a dynamic project

create_dynamic_project
Idempotent

Creates an empty Node.js, PHP or Python project in the selected Personal space or workspace, with its hosting address and persistent data directory. 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_dynamic_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
labelYes
domainNo
manifestNoRead runtime_contract first. Omitted settings retain the existing project configuration. PHP start is empty for the managed server.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context by naming a server-side condition ('project_destination_required identifies an unresolved destination') and listing what gets provisioned, but it omits permission requirements and what happens on partial failure.

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 compact sentences with the creation scope front-loaded and the destination caveat second. No filler, though the dangling 'project_destination_required' identifier appears without any framing of what it is.

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?

For a 6-parameter, nested-object creation tool with no output schema, the description covers destination and artifacts but leaves the manifest, idempotency usage, and post-creation state to the schema. It is adequate but relies heavily on structured fields to be callable correctly.

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?

With 50% schema description coverage, the description compensates only for the destination parameter, matching the schema's own workspace_id note about omitting it when undecided. The manifest object — the most complex parameter — is not explained in the description at all, though the schema itself carries a 'Read runtime_contract first' note.

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 (creates) and resource (dynamic project) plus supported runtimes (Node.js, PHP, Python) and the result artifacts (hosting address, persistent data directory). It does not explicitly contrast with the sibling create_project or configure_dynamic_project, so the agent must infer that this is the dynamic/runtime-backed variant.

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?

The description implies this is the creation step for runtime-backed projects and mentions that 'project_destination_required' signals an unresolved destination, which hints at a prerequisite flow. However, it never says when to choose this over create_project, nor that configure_dynamic_project/runtime_contract should be consulted before supplying a manifest.

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