Spala Public MCP

Get Project Public Context

project_get_public_context

Read-onlyIdempotent

For embeddings and similarity search, use Vector fields and native Similarity Search with owner/tenant filters. Do not store search embeddings as JSON arrays or compute cosine similarity in Custom Code. Keep embedding dimensions/model consistent. If pgvector is unavailable, request database administrator setup; do not substitute JSON. Migrating existing embeddings requires approval. Includes native-block and filter guidance, addon discovery, and the requirement to justify narrowly scoped Custom Code. 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
`nativeBuildGuidance`	No
`vectorSearchGuidance`	No
`addonDiscoveryGuidance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026
- addedOutput schema / properties / addonDiscoveryGuidance
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / nativeBuildGuidance
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedOct 8, 2026
- addedOutput schema / properties / vectorSearchGuidance
```
Added value: +{
+  "type": "string"
+}
```

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

C2.9/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely useful context: 'AUTH REQUIRED; READ-ONLY' and an explicit non-disclosure contract (no tokens, private source code, unrelated customer data, or executable installer arguments). That exposure boundary is not derivable from the annotations and materially informs the agent's expectations.

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

Conciseness2/5

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

Roughly five of seven sentences are an embeddings/vector-search policy preamble unrelated to this tool, and the one sentence describing the tool's behavior is last rather than front-loaded. The text is long but the off-topic material does not earn its place here.

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?

The tool is simple (single mutually-exclusive selector), the schema is fully documented, and an output schema exists, so the description needn't explain return fields. It supplies auth and exposure constraints, but never clarifies what 'public context' contains or how it relates to project_get_mcp_manifest, leaving a modest gap.

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% and the oneOf plus mutual-exclusion rule is already stated in the schema. The description adds no parameter meaning (no clarification of projectId vs subdomain vs organizationId), so the baseline 3 applies.

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

Purpose3/5

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

The actual purpose arrives only in the final sentence: 'Returns documented MCP handoff fields for one accessible project.' The preceding five sentences describe embedding/vector-search policy, which is unrelated to what this tool does and buries the verb+resource. No sibling (project_list, project_select, project_get_mcp_manifest) is named to differentiate scope.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative-selection guidance for fetching project context. The 'use Vector fields... do not compute cosine similarity' instructions are guidance for a different task (embeddings), not for invoking this tool. An agent learns nothing about when this tool beats project_select or project_list.

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.