Skip to main content
Glama

Spala Public MCP

by ai.spala
OverviewDiscussionsAdmin

List Spala Addons

addon_list
Read-onlyIdempotent

Lists public Spala addons and integrations matching an optional query. Curated public subset; use project addons_search/addons_get to verify availability and installed status. Invoke for Telegram bots and CRM, webhooks, outbound HTTP API calls, transactional email, media uploads, and realtime messaging. Returns addon ids, names, descriptions, and tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of catalog entries to return.
queryNoOptional filter phrase for matching public Spala templates or addons by name, tag, or use case.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
addonsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Public Spala addons and integrations matching the optional query.",
+  "properties": {
+    "addons": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "addons"
+  ],
+  "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 catalog search and result limit for public Spala planning resources."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of catalog entries to return."
    • addedInput schema / properties / query / description
      Added value: +"Optional filter phrase for matching public Spala templates or addons by name, tag, or use case."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds real behavioral context: this is a 'curated public subset', i.e. results are not authoritative for availability or installed status, which is a meaningful limitation the annotations do not convey. It stops short of stating pagination or whether the catalog is cached/static.

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?

Four compact sentences, front-loaded with the purpose and the subset caveat before the use-case triggers. Every sentence contributes, though the trailing return-field list is mildly redundant given the output schema exists.

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 two-parameter read-only listing tool with full schema coverage, an output schema, and complete annotations, the definition covers scope, limitations, triggers, and routing to alternatives. Nothing essential is missing; only minor return/pagination behavior is left unstated.

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 both parameters (limit, query) are fully documented in the schema, so the baseline is 3. The description restates the optional query filter and the return fields, but adds no syntax, matching behavior, or default/ceiling detail beyond what the schema already provides.

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 precise verb and resource ('Lists public Spala addons and integrations') plus the scoping condition ('matching an optional query'). The word 'public subset' distinguishes it from internal/project-scoped catalog tools and from template_list.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers ('Telegram bots and CRM, webhooks, outbound HTTP API calls, transactional email, media uploads, realtime messaging') and names the alternatives to use for verification ('project addons_search/addons_get'). The condition that selects the alternative is stated, not inferred.

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