spala_helpReturns a human-readable overview of Spala, canonical start URLs, and the boundary between public discovery and project-scoped backend MCPs. Invoke for product, setup, or integration orientation. This read-only tool requires no authentication and does not access or modify project data.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| markdown | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds 'requires no authentication' and 'does not access or modify project data,' providing stronger guarantees beyond the basic hints. This additional context is valuable and does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, with the first sentence front-loading the core purpose and the second providing usage and safety context. Each sentence earns its place, with no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple no-parameter help tool with a rich output schema and good annotations, the description covers the essential aspects: what is returned (overview, URLs, boundary), when to use it (orientation), and its safety profile (read-only, no auth, no project access). This is sufficient for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The schema already states 'No arguments' and the description adds no param-specific details, but no such details are needed. The description's focus on output and usage compensates for the lack of parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'Returns a human-readable overview of Spala, canonical start URLs, and the boundary between public discovery and project-scoped backend MCPs.' This is a specific verb+resource and distinguishes it from sibling tools like docs_search or spala_get_tool_map by focusing on orientation and boundary clarification.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear invocation context: 'Invoke for product, setup, or integration orientation.' It does not explicitly mention alternatives or when not to use the tool, but the context is specific enough for an agent to know when this help tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear, distinct purposes, but project_connect and project_select are essentially aliases, which introduces ambiguity. Additionally, spala_help and docs_search could overlap, but they are differentiated by scope.
The naming mostly follows a <domain>_<verb> pattern, with some exceptions like spala_help (no verb) and the duplicate project_select. Overall, the pattern is predictable and readable.
16 tools is well-scoped for a public platform that handles accounts, organizations, projects, addons, templates, and documentation. Each tool earns its place without being excessive.
Core workflows like creating and connecting projects are covered, but there are notable gaps: no tools for updating or deleting accounts, organizations, or projects. Also, addons and templates are only listable, missing management operations.