Spala Public MCP

Get Project Public Context

project_get_public_context

Read-onlyIdempotent

AUTH REQUIRED; READ-ONLY. Returns documented MCP handoff fields for one accessible project without exposing tokens, private source code, unrelated customer data, or executable installer arguments.

Input Schema

TableJSON Schema

Name	Required	Description
`projectId`	No	Exact Spala project ID. Mutually exclusive with subdomain.
`subdomain`	No	Exact project subdomain returned by the Spala projects API. Mutually exclusive with projectId.
`organizationId`	No	Optional organization ID returned for the signed-in account.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`handoff`	Yes
`project`	Yes
`intentBoundary`	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": "Safe documented project handoff context without credentials or executable installer arguments.",
+  "properties": {
+    "handoff": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "intentBoundary": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "project": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "project",
+    "intentBoundary",
+    "handoff"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedJul 15, 2026

changedInput schema / description

Previous value: -"Provide exactly one project selector: projectId or slug."New value: +"Provide exactly one project selector: projectId or subdomain. organizationId is optional when selecting by subdomain."

changedInput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "projectId": {
-        "description": "Exact Spala project ID. Mutually exclusive with slug.",
-        "maxLength": 256,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "projectId"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "slug": {
-        "description": "Exact Spala project slug. Mutually exclusive with projectId.",
-        "maxLength": 256,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "slug"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "projectId": {
+        "description": "Exact Spala project ID. Mutually exclusive with subdomain.",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "projectId"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "organizationId": {
+        "description": "Optional organization ID returned for the signed-in account.",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      },
+      "subdomain": {
+        "description": "Exact project subdomain returned by the Spala projects API. Mutually exclusive with projectId.",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "subdomain"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / organizationId

Added value: +{
+  "description": "Optional organization ID returned for the signed-in account.",
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / projectId / description

Previous value: -"Exact Spala project ID. Mutually exclusive with slug."New value: +"Exact Spala project ID. Mutually exclusive with subdomain."

removedInput schema / properties / slug

Removed value: -{
-  "description": "Exact Spala project slug. Mutually exclusive with projectId.",
-  "maxLength": 256,
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / properties / subdomain

Added value: +{
+  "description": "Exact project subdomain returned by the Spala projects API. Mutually exclusive with projectId.",
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}

Changed9 schema fields changedJul 11, 2026

removedInput schema / $schema

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

addedInput schema / description

Added value: +"Provide exactly one project selector: projectId or slug."

addedInput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "projectId": {
+        "description": "Exact Spala project ID. Mutually exclusive with slug.",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "projectId"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "slug": {
+        "description": "Exact Spala project slug. Mutually exclusive with projectId.",
+        "maxLength": 256,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / projectId / description

Added value: +"Exact Spala project ID. Mutually exclusive with slug."

addedInput schema / properties / projectId / maxLength
```
Added value: +256
```
addedInput schema / properties / projectId / minLength
```
Added value: +1
```

addedInput schema / properties / slug / description

Added value: +"Exact Spala project slug. Mutually exclusive with projectId."

addedInput schema / properties / slug / maxLength
```
Added value: +256
```
addedInput schema / properties / slug / minLength
```
Added value: +1
```

First observedJul 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful context beyond this by specifying that the tool does not expose tokens, private source code, unrelated customer data, or executable installer arguments, and that auth is required. This supplements the annotation coverage.

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?

The description is a single sentence, front-loaded with 'AUTH REQUIRED; READ-ONLY,' and every phrase earns its place. It is concise without sacrificing key information.

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

Completeness4/5

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

With a comprehensive schema (including oneOf selector) and an output schema present, the description covers the core purpose and safety exclusions. It does not repeat return-value details or selector rules, which are already in the schema. Minor room for improvement: it could explicitly mention that exactly one of projectId or subdomain is required, but that is covered structurally.

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 100%, so the schema fully documents projectId, subdomain, and organizationId, including mutual exclusivity. The description does not add parameter-specific meaning, so it meets the baseline but does not go beyond it.

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?

The description uses a specific verb ('Returns') and identifies the resource ('documented MCP handoff fields for one accessible project'). It clearly distinguishes this from sibling tools by focusing on public context retrieval and explicitly listing exclusions, making the purpose unambiguous.

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 usage context (retrieving public context for a project) and notes auth requirements, but it does not explicitly mention alternatives or when not to use this tool. Sibling tools like project_select or project_get_mcp_manifest exist, but no exclusions or comparisons are provided.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.