Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

app

Destructive

List, inspect, install, and uninstall site applications by action, enabling or removing features on the current WebCake storefront.

Instructions

Apps of the site (install, configure, remove). Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_apps: Which applications are installed / enabled on the site — and which are not — in ONE call.

  • get_app: Get one installed app by its type code (returns null if not installed).

  • install_app: Install (register) an application on the current site so its features become usable.

  • uninstall_app: Uninstall (remove) an installed application from the current site.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "app"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoApp subscription id (from list_apps / get_app) [uninstall_app]
appNoApp to install (by name) [install_app]
helpNoReturn the action's full documentation and argument schema instead of running it
typeNoApp type — a code (e.g. [get_app]
actionYesWhich operation to run
is_activeNoActivate the app on install [install_app]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the tool is not read-only and is destructive, so the description mainly needs to add operational context. It adds useful details such as get_app returning null when not installed, install making features usable, and uninstall removing an app, but it omits permissions, side effects/data-loss implications, idempotency, and mutation return behavior.

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?

The description is front-loaded with purpose and routing, then uses compact action bullets that each earn their place. There is minor redundancy in listing install/remove in the opening sentence and again in bullets, and 'configure' is mentioned even though no configure action exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the full action set and input routing, and the schema fully documents parameters, so an agent can select and invoke an action. However, with no output schema, the description gives return behavior only for get_app and does not explain what list_apps, install_app, or uninstall_app return; the help mode mitigates this but does not fully compensate.

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 schema already documents `id`, `app`, `help`, `type`, `action`, and `is_active` with relevant tags. The description reinforces the `action` routing and `help:true` behavior but adds little beyond the schema about the parameters themselves.

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 names the resource (site apps) and explicitly enumerates the four operations: list_apps, get_app, install_app, and uninstall_app. This lets an agent distinguish the tool's scope and internal actions without opening the schema.

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?

It explicitly tells the caller to choose an operation via `action` and pass that action's arguments, with `help:true` as an escape hatch for full docs. The action bullets imply when each operation applies, but it does not state when not to use this tool or name sibling alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.