Spala Public MCP

Create Spala Project

project_create

Destructive

AUTH REQUIRED; WRITES TO THE SPALA CONTROL PLANE. Creates a real Spala project with the supplied project name in an accessible organization. Provisioning is asynchronous; follow the returned retry interval and bounded retry guidance, never create a duplicate. Accepts an organization id when multiple organizations are available and automatically scopes a sole organization. This operation is not idempotent.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Human-readable name for the new Spala project.
`organizationId`	No	Organization ID returned for the signed-in account. Optional only when exactly one organization is available.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`next`	Yes
`created`	Yes
`project`	Yes
`organization`	Yes
`provisioning`	Yes
`mcpUrlResolved`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "New Spala project and provisioning guidance for project MCP handoff.",
+  "properties": {
+    "created": {
+      "type": "boolean"
+    },
+    "mcpUrlResolved": {
+      "type": "boolean"
+    },
+    "next": {
+      "type": "string"
+    },
+    "organization": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "project": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "provisioning": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "organization",
+    "project",
+    "created",
+    "mcpUrlResolved",
+    "provisioning",
+    "next"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedJul 15, 2026

changedInput schema / description

Previous value: -"Auth-gated dry-run project creation request. In this standalone public MCP deployment it validates shape only and cannot create a real project."New value: +"Create a real Spala project in an organization available to the authenticated user."

removedInput schema / properties / description

Removed value: -{
-  "description": "Optional short product/backend description for planning. Do not include secrets or private customer data.",
-  "maxLength": 2000,
-  "minLength": 1,
-  "type": "string"
-}

changedInput schema / properties / name / description

Previous value: -"Human-readable project name to validate for a future Spala backend project."New value: +"Human-readable name for the new Spala project."

addedInput schema / properties / organizationId

Added value: +{
+  "description": "Organization ID returned for the signed-in account. Optional only when exactly one organization is available.",
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / template

Removed value: -{
-  "description": "Optional public template id or template hint from template_list.",
-  "maxLength": 128,
-  "minLength": 1,
-  "type": "string"
-}

Changed5 schema fields changedJul 12, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / description

Added value: +"Auth-gated dry-run project creation request. In this standalone public MCP deployment it validates shape only and cannot create a real project."

addedInput schema / properties / description / description

Added value: +"Optional short product/backend description for planning. Do not include secrets or private customer data."

addedInput schema / properties / name / description

Added value: +"Human-readable project name to validate for a future Spala backend project."

addedInput schema / properties / template / description

Added value: +"Optional public template id or template hint from template_list."

Changed5 schema fields changedJul 11, 2026
- addedInput schema / properties / description / maxLength
```
Added value: +2000
```
- addedInput schema / properties / description / minLength
```
Added value: +1
```
- addedInput schema / properties / name / maxLength
```
Added value: +120
```
- addedInput schema / properties / template / maxLength
```
Added value: +128
```
- addedInput schema / properties / template / minLength
```
Added value: +1
```
First observedJul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the description adds real value on top: auth is required, the write targets the control plane, and provisioning is asynchronous with retry guidance to avoid duplicate creation. It stops short of describing the actual returned payload or what side effects 'destructive' entails.

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

Conciseness5/5

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

Critical constraints (auth, write, control plane) are front-loaded in the first clause, and every following sentence carries a distinct operational fact: async provisioning, retry behavior, no duplicates, organization scoping, non-idempotency. No wasted text.

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

Completeness5/5

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

With an output schema present, return values need not be explained. The description covers the remaining agent-critical concerns for a non-idempotent, async, authenticated write: auth, scoping, retry handling, and duplicate avoidance.

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 coverage is 100%, so both parameters are already documented in the schema, including the 'optional only when exactly one organization is available' condition. The description restates that condition rather than adding new syntax or format detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Creates a real Spala project') plus scope ('in an accessible organization'), which cleanly separates it from siblings like project_list, project_select, and organization_create. An agent can identify what this tool produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear condition for the optional parameter ('when multiple organizations are available') and a strong behavioral directive ('never create a duplicate'). It lacks an explicit pointer to the alternative tool for checking existing projects, but the context for use is unambiguous.

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

All Spala Public MCP tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.