Skip to main content
Glama

Spala Public MCP

by ai.spala
OverviewDiscussionsAdmin

Search Spala Documentation

docs_search
Read-onlyIdempotent

Searches the public Spala agent-facing documentation index by query. Invoke for setup, OAuth, installer, public-versus-project MCP, pricing, limits, security, templates, addons, native blocks, filters, Custom Code alternatives, or project handoff questions. Returns ranked docs entries with URLs and summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of ranked documentation results to return.
queryNoOptional search phrase. Use words such as auth, OAuth, MCP, templates, addons, pricing, limits, frontend handoff, or project handoff.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Ranked public documentation search results.",
+  "properties": {
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "results"
+  ],
+  "type": "object"
+}
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / description
      Added value: +"Optional text search and result limit for public Spala documentation."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of ranked documentation results to return."
    • addedInput schema / properties / query / description
      Added value: +"Optional search phrase. Use words such as auth, OAuth, MCP, templates, addons, pricing, limits, frontend handoff, or project handoff."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld=false, so safety is covered. The description adds meaningful scope context the annotations do not: that the index is public and agent-facing, distinguishing it from project-specific documentation. It also notes the return shape, though that is partly redundant with the output schema.

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?

Three sentences, front-loaded with the core purpose, then invocation contexts, then return behavior. The trigger list is long but each term earns its place as a searchable keyword; only minor trimming would help.

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 an output schema, annotations, and full parameter coverage, the description is nearly complete. It covers purpose, scope, triggers, and return shape; only explicit routing against sibling help tools is missing.

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% and both parameters are optional with defaults, so the schema carries parameter meaning. The description only restates 'by query' and adds no format or syntax detail beyond what the schema already provides; 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 (Searches), resource (public Spala agent-facing documentation index), and mechanism (by query). It is clearly separable from siblings like spala_help, spala_get_tool_map, and template_list, which serve different functions.

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 an explicit and unusually rich trigger list (setup, OAuth, installer, pricing, limits, project handoff, etc.), which tells the agent exactly when to reach for this tool. It stops short of naming when NOT to use it or pointing to alternatives like spala_help.

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

Resources