Skip to main content
Glama

Spala Public MCP

by ai.spala
OverviewDiscussionsAdmin

Start Spala

spala_start
Read-onlyIdempotent

AUTH REQUIRED; READ-ONLY STARTUP. Invoke after OAuth to begin Spala account or project setup. Returns a versioned startup phase with account readiness, organizations, safely scoped project discovery, and one explicit next action. Reports missing account fields, automatically scopes a sole organization, and returns all accessible choices when multiple organizations exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYes
phaseYes
projectsYes
nextActionYes
accountSetupYes
authenticatedYes
organizationsYes
schemaVersionYes
backendProviderYes
installerMaintenanceYes
selectedOrganizationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / installerMaintenance
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "schemaVersion",
-  "phase",
-  "authenticated",
-  "backendProvider",
-  "user",
-  "accountSetup",
-  "organizations",
-  "projects",
-  "nextAction"
-]New value: +[
+  "schemaVersion",
+  "phase",
+  "authenticated",
+  "backendProvider",
+  "user",
+  "accountSetup",
+  "organizations",
+  "projects",
+  "installerMaintenance",
+  "nextAction"
+]
  2. Changed2 schema fields changed
    • removedOutput schema / properties / installerMaintenance
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • changedOutput schema / required
      Previous value: -[
-  "schemaVersion",
-  "phase",
-  "authenticated",
-  "backendProvider",
-  "user",
-  "accountSetup",
-  "organizations",
-  "projects",
-  "installerMaintenance",
-  "nextAction"
-]New value: +[
+  "schemaVersion",
+  "phase",
+  "authenticated",
+  "backendProvider",
+  "user",
+  "accountSetup",
+  "organizations",
+  "projects",
+  "nextAction"
+]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / installerMaintenance
      Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "schemaVersion",
-  "phase",
-  "authenticated",
-  "backendProvider",
-  "user",
-  "accountSetup",
-  "organizations",
-  "projects",
-  "nextAction"
-]New value: +[
+  "schemaVersion",
+  "phase",
+  "authenticated",
+  "backendProvider",
+  "user",
+  "accountSetup",
+  "organizations",
+  "projects",
+  "installerMaintenance",
+  "nextAction"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Authenticated startup state with account readiness, project discovery, and one next action.",
+  "properties": {
+    "accountSetup": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "authenticated": {
+      "type": "boolean"
+    },
+    "backendProvider": {
+      "type": "string"
+    },
+    "nextAction": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "organizations": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "phase": {
+      "type": "string"
+    },
+    "projects": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "schemaVersion": {
+      "type": "integer"
+    },
+    "selectedOrganizationId": {
+      "type": "string"
+    },
+    "user": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "phase",
+    "authenticated",
+    "backendProvider",
+    "user",
+    "accountSetup",
+    "organizations",
+    "projects",
+    "nextAction"
+  ],
+  "type": "object"
+}
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description adds meaningful behavioral detail: auth requirement, read-only startup nature, versioned output, account readiness, scoping behavior for a sole organization, and choice reporting for multiple organizations. It enriches the readOnlyHint and opens up what an agent can expect without contradicting any annotation.

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 three sentences, front-loaded with 'AUTH REQUIRED; READ-ONLY STARTUP' and then immediately states the invocation condition. Every sentence contributes distinct value: return shape, account fields, organization scoping logic. No filler or repeated schema content.

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?

Given there are no parameters and an output schema exists, the description provides complete operational context: when to call, what it returns, why it is safe, and how it behaves under different organizational configurations. Nothing an agent needs to decide invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and late-stage schema description coverage already saying nothing is needed, the description has no parameter details to add. The tool requires no arguments, and this is handled well by the schema. Baseline 4 is appropriate for a zero-argument tool operating at a call result.

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 clearly identifies the tool's purpose: a read-only startup routine invoked after OAuth to begin Spala account or project setup. It moves well beyond the name with explicit details about returning a versioned startup phase and one next action, making it easy for an agent to distinguish from generic list or status tools.

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?

The description gives a concrete precondition in 'Invoke after OAuth' and explains the logic for sole versus multiple organizations, but it does not explicitly mention when not to use this tool or name alternatives in the sibling set. This is clear context with no exclusions or alternative routing, which matches the 'clear context, but no exclusions' level.

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 toolsInspect
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.

Resources