Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_apps

Read-only

Returns installed and enabled storefront apps plus apps not installed in one call, so you can audit site capabilities without checking each app type.

Instructions

Which applications are installed / enabled on the site — and which are not — in ONE call. Returns installed[] (id, type, name, enabled) plus not_installed[] (app names). Do NOT call get_app per type to answer "which apps are on"; use get_app only for one app's settings. App type codes: 0=product_review, 1=articles_review, 2=automation, 3=telegram, 4=affiliates, 5=multilingual, 6=appointment, 7=send_email, 8=botcake, 9=sale_channel, 10=product_design, 11=auth_otp, 12=personal_product_design, 14=course, 15=zalo_mini_app, 16=cms, 17=recaptcha, 18=pwa.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A4.6/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes safety. The description adds useful behavior beyond annotations: it is a single-call enumeration, returns installed[] with id/type/name/enabled and not_installed[] names, and avoids N calls to get_app. It does not explicitly state site-context or permission assumptions, so it is not fully exhaustive.

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: purpose first, then return shape, then sibling guidance, then type codes. The long type-code enumeration is dense but justified because there is no output schema and the numeric codes would otherwise be opaque. Slightly more compact grouping could improve scanability.

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?

With no parameters and no output schema, the description carries the full burden of explaining what is returned. It does so by naming the installed[] fields, the not_installed[] contents, and the app type code meaning, while the readOnly annotation covers the safety profile.

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?

The tool takes no input parameters, so the parameter schema has nothing to explain. The description's app type code mapping helps interpret returned type values rather than input parameters, which is useful context but not input-parameter guidance.

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 states a specific capability: listing installed/enabled applications and not-installed apps in one call. It distinguishes this from sibling get_app by saying get_app is only for one app's settings. An agent can immediately tell what the tool does and what it returns.

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?

It gives explicit routing guidance: do NOT call get_app per app type to answer which apps exist, and use get_app only for settings. This directly names the relevant alternative and the condition that selects each tool.

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

Deploy Server

Other Tools