Spala Public MCP

Get Spala Onboarding

spala_get_onboarding

Read-onlyIdempotent

Returns machine-readable Spala onboarding information for MCP clients. Includes product scope, OAuth metadata, supported installer client identifiers, authenticated project-handoff status, workflow stages, and canonical links.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`installerVersion`	No	Optional project proxy installer version already known from its registration command. Do not supply the Claude/Codex application version or read credential stores.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes
`product`	Yes
`workflow`	Yes
`publicMcpRole`	Yes
`handoffExample`	No
`intentBoundary`	No
`projectMcpRole`	Yes
`supportedInstallerClients`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

removedInput schema / description

Removed value: -"No arguments. Call this tool with an empty object."

addedInput schema / properties / installerVersion

Added value: +{
+  "description": "Optional project proxy installer version already known from its registration command. Do not supply the Claude/Codex application version or read credential stores.",
+  "maxLength": 64,
+  "type": "string"
+}

Changed1 schema field changedJul 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Anonymous compatibility onboarding and canonical Spala workflow links.",
+  "properties": {
+    "handoffExample": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "intentBoundary": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "product": {
+      "type": "string"
+    },
+    "projectMcpRole": {
+      "type": "string"
+    },
+    "publicMcpRole": {
+      "type": "string"
+    },
+    "supportedInstallerClients": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "urls": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "workflow": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "product",
+    "publicMcpRole",
+    "projectMcpRole",
+    "workflow",
+    "urls"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJul 12, 2026

removedInput schema / $schema

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

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / description

Added value: +"No arguments. Call this tool with an empty object."

First observedJul 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a content inventory (OAuth metadata, installer client identifiers, project-handoff status, workflow stages), but since an output schema exists this largely restates return values rather than disclosing new behavior such as auth prerequisites or caching semantics.

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 tight sentences with no filler, and the core purpose is front-loaded before the payload enumeration. The second sentence is a dense list, but every item maps to a distinct part of the onboarding payload.

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?

For a zero-required-parameter, read-only introspection tool with full annotation coverage, a complete output schema, and a fully documented parameter, the definition carries enough to invoke it correctly. The main omission is routing guidance among the many similarly named setup/onboarding siblings.

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 single optional parameter already carries strong guidance, including the negative instruction not to pass the Claude/Codex application version or read credential stores. The description adds nothing about the parameter, so the baseline 3 applies.

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 and resource ('Returns machine-readable Spala onboarding information for MCP clients') and enumerates the payload categories, so the agent knows exactly what it gets back. It does not, however, contrast itself with near-neighbours like spala_help, spala_start, or project_get_public_context, which look plausibly similar.

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?

There is no when-to-use or when-not-to-use guidance; the only contextual cue is the phrase 'for MCP clients'. An agent cannot tell from the description whether this should be called before spala_start, instead of spala_help, or only during first-time setup.

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.