Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_combo_items

Read-only

Retrieve the required products and free bonus items that form a combo by passing its combo product ID, so you can inspect combo contents before building storefront pages.

Instructions

Get items (products/variations) and bonus products that compose a combo. Returns combo_items (required items with count) and bonus_items (free gifts)

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": {
      "combo_product_id": "<combo_product_id>"
    },
    "name": "get_combo_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
combo_product_idYesCombo product ID
is_variation_bonusNoWhether bonus items are variation-based

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description goes further by naming the two return groups (combo_items with counts, bonus_items as free gifts), which is useful since no output schema exists, but it says nothing about pagination, empty results, or error behavior for an invalid combo ID.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, return shape stated up front, zero filler words.

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 simple two-parameter read tool with no output schema, the description covers what is fetched and the shape of the response, which is enough for correct invocation. Minor gaps remain around the is_variation_bonus effect and empty/error cases.

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% with only two params, so the schema already documents combo_product_id and is_variation_bonus. The description adds no syntax, format, or semantics beyond the implied combo linkage, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (items/bonus products composing a combo), and clarifies that it returns the components of a combo rather than the combos themselves. It is distinguishable from list_combos, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

The description says what is fetched but gives no when-to-use, no prerequisite framing (e.g. 'given a combo_product_id from list_combos'), and no guidance on choosing this over list_combos or get_product. Usage is only inferable from the resource name.

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