Skip to main content
Glama

sb_store

Builds and publishes checkout pages, syncs payment and delivery options, and configures forms, menus, overlays, cart, apps, and shared sections for a Store Builder site.

Instructions

Run a store flow that must happen in a fixed order. action:"checkout" makes the order form, configures it, saves its fields with this store's real payment and delivery options, then creates and PUBLISHES the checkout page — /checkout 404s without all four. action:"checkout_sync" re-reads the store's payment and delivery methods into every existing order form and republishes the checkout page — run it after adding a shipping method or switching on a gateway, since the form keeps the options it was saved with. action:"form" seeds any of the platform's other form templates (login, contact, booking, stay and more — settings merge into the record) with its own field document, which is the part that cannot be guessed. action:"chrome" gives every page ONE shared header (footer:true — footer) built on a real site menu of page/category/product references: site name, desktop menu, mobile drawer, search, cart and account icons — the gap sb_review reports as siteChrome. action:"menu" binds a menu node on the open page to the site's menu and resolves its links, the way the editor does. action:"overlay_attach" puts a pop-up on the open page (kind:"popup") or points a list-dataset at a quick-view panel (kind:"quickview", list_id), creating either from the platform's own seed when overlay_id is omitted, and re-reads the page afterwards as the editor must. action:"cart" creates the site's cart drawer from the editor's seed when it has none — without it every open_cart control opens nothing. action:"app" installs one of the platform's built-in apps (app_key) and creates the pages it needs that installing it does not — today only "courses" has any, from the platform's own scaffold; every other key installs with nothing further to build. action:"global_attach" puts an EXISTING shared section (global_id) on the open page and action:"global_detach" takes it off, writing the reference the platform reads and placing it in the band ROOT's child order demands — the answer for a page that is missing the site's header, where action:"chrome" would wrongly build a second one. action:"global_promote" turns a section on the open page (node_id) into a NEW shared section (global_kind header|footer|custom, default custom) and leaves the page referencing it; action:"template_save" saves one as a section template (name; template_share sends one to the org's review). site_template offers the whole site as its org's template (org_id attaches first; site_template_remove withdraws). Dry run returns the plan.

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": "sb_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoaction:"overlay_attach" — which kind of overlay to attach
nameNoaction:"form" — the form's name in the merchant's list. action:"overlay_attach" with no overlay_id — the new pop-up/quick-view's name. "chrome" — the header's site name.
actionYes
footerNoaction:"chrome" — build a shared FOOTER instead of a header
org_idNo
app_keyNoaction:"app" — which built-in app to install
dry_runNo
list_idNoaction:"overlay_attach" kind:"quickview" — the list-dataset node on the open page
menu_idNo
node_idNoaction:"menu" — the menu node; "global_promote"/"template_save" — the section; "form" — a node of the open page to place it in
site_idNo
headlineNo
languageNoCopy language, default vi
settingsNoaction:"form" {booking:{maxPerSlot:2}}
templateNoaction:"form" — which of the platform's own form templates to seed
global_idNoaction:"global_attach"/"global_detach" — the shared section; omitted on attach it lists the site's own
page_nameNo
categoriesNotemplate_save/site_template: slugs from the dry run
overlay_idNoaction:"overlay_attach" — an existing overlay; omit to create one from the seed
relocalizeNoaction:"cart" — rewrite an EXISTING drawer's seed words that are in another language to the site locale's (edited text untouched), and turn a gallery line thumbnail into a single image; needs a page of the site open
descriptionNotemplate_save/site_template: one sentence, what it is for
global_kindNo
template_idNoaction:"template_save" — overwrite this template's content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.107.1
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "checkout",
      -  "checkout_sync",
      -  "form",
      -  "chrome",
      -  "menu",
      -  "overlay_attach",
      -  "cart",
      -  "app",
      -  "global_attach",
      -  "global_detach",
      -  "global_promote",
      -  "template_save"
      -]New value: +[
      +  "checkout",
      +  "checkout_sync",
      +  "form",
      +  "chrome",
      +  "menu",
      +  "overlay_attach",
      +  "cart",
      +  "app",
      +  "global_attach",
      +  "global_detach",
      +  "global_promote",
      +  "template_save",
      +  "site_template",
      +  "site_template_remove",
      +  "template_share"
      +]
    • addedInput schema / properties / categories
      Added value: +{
      +  "description": "template_save/site_template: slugs from the dry run",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "template_save/site_template: one sentence, what it is for",
      +  "type": "string"
      +}
    • addedInput schema / properties / org_id
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.103.0
    • changedInput schema / properties / node_id / description
      Previous value: -"action:\"menu\" — the menu node; \"global_promote\"/\"template_save\" — the section"New value: +"action:\"menu\" — the menu node; \"global_promote\"/\"template_save\" — the section; \"form\" — a node of the open page to place it in"
  3. Changed1 schema field changedv0.98.3
    • changedInput schema / properties / name / description
      Previous value: -"action:\"form\" — the form's name in the merchant's list. action:\"overlay_attach\" with no overlay_id — the new pop-up/quick-view's name."New value: +"action:\"form\" — the form's name in the merchant's list. action:\"overlay_attach\" with no overlay_id — the new pop-up/quick-view's name. \"chrome\" — the header's site name."
  4. Changed6 schema fields changedv0.89.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "checkout",
      -  "checkout_sync",
      -  "form",
      -  "chrome",
      -  "menu",
      -  "overlay_attach",
      -  "cart",
      -  "app",
      -  "global_attach",
      -  "global_detach"
      -]New value: +[
      +  "checkout",
      +  "checkout_sync",
      +  "form",
      +  "chrome",
      +  "menu",
      +  "overlay_attach",
      +  "cart",
      +  "app",
      +  "global_attach",
      +  "global_detach",
      +  "global_promote",
      +  "template_save"
      +]
    • changedInput schema / properties / app_key / enum
      Previous value: -[
      -  "mail",
      -  "multilingual",
      -  "agent",
      -  "chat",
      -  "booking",
      -  "loyalty",
      -  "payments",
      -  "courses"
      -]New value: +[
      +  "mail",
      +  "multilingual",
      +  "agent",
      +  "chat",
      +  "booking",
      +  "loyalty",
      +  "payments",
      +  "courses",
      +  "shipping",
      +  "pos",
      +  "tickets"
      +]
    • addedInput schema / properties / global_kind
      Added value: +{
      +  "enum": [
      +    "header",
      +    "footer",
      +    "custom"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / node_id / description
      Previous value: -"action:\"menu\" — the menu node on the open page"New value: +"action:\"menu\" — the menu node; \"global_promote\"/\"template_save\" — the section"
    • addedInput schema / properties / settings
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "action:\"form\" {booking:{maxPerSlot:2}}",
      +  "type": "object"
      +}
    • addedInput schema / properties / template_id
      Added value: +{
      +  "description": "action:\"template_save\" — overwrite this template's content",
      +  "type": "string"
      +}
  5. Changed1 schema field changedv0.76.3
    • changedInput schema / properties / relocalize / description
      Previous value: -"action:\"cart\" — rewrite an EXISTING drawer's seed words that are in another language to the site locale's (edited text untouched); needs a page of the site open"New value: +"action:\"cart\" — rewrite an EXISTING drawer's seed words that are in another language to the site locale's (edited text untouched), and turn a gallery line thumbnail into a single image; needs a page of the site open"
  6. Changed2 schema fields changedv0.69.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "checkout",
      -  "form",
      -  "chrome",
      -  "menu",
      -  "overlay_attach",
      -  "app",
      -  "global_attach",
      -  "global_detach"
      -]New value: +[
      +  "checkout",
      +  "checkout_sync",
      +  "form",
      +  "chrome",
      +  "menu",
      +  "overlay_attach",
      +  "cart",
      +  "app",
      +  "global_attach",
      +  "global_detach"
      +]
    • addedInput schema / properties / relocalize
      Added value: +{
      +  "description": "action:\"cart\" — rewrite an EXISTING drawer's seed words that are in another language to the site locale's (edited text untouched); needs a page of the site open",
      +  "type": "boolean"
      +}
  7. Changed9 schema fields changedv0.63.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "checkout",
      -  "form",
      -  "chrome"
      -]New value: +[
      +  "checkout",
      +  "form",
      +  "chrome",
      +  "menu",
      +  "overlay_attach",
      +  "app",
      +  "global_attach",
      +  "global_detach"
      +]
    • addedInput schema / properties / app_key
      Added value: +{
      +  "description": "action:\"app\" — which built-in app to install",
      +  "enum": [
      +    "mail",
      +    "multilingual",
      +    "agent",
      +    "chat",
      +    "booking",
      +    "loyalty",
      +    "payments",
      +    "courses"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / global_id
      Added value: +{
      +  "description": "action:\"global_attach\"/\"global_detach\" — the shared section; omitted on attach it lists the site's own",
      +  "type": "string"
      +}
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "action:\"overlay_attach\" — which kind of overlay to attach",
      +  "enum": [
      +    "popup",
      +    "quickview"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / list_id
      Added value: +{
      +  "description": "action:\"overlay_attach\" kind:\"quickview\" — the list-dataset node on the open page",
      +  "type": "string"
      +}
    • addedInput schema / properties / menu_id
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"action:\"form\" — the form's name in the merchant's list"New value: +"action:\"form\" — the form's name in the merchant's list. action:\"overlay_attach\" with no overlay_id — the new pop-up/quick-view's name."
    • addedInput schema / properties / node_id
      Added value: +{
      +  "description": "action:\"menu\" — the menu node on the open page",
      +  "type": "string"
      +}
    • addedInput schema / properties / overlay_id
      Added value: +{
      +  "description": "action:\"overlay_attach\" — an existing overlay; omit to create one from the seed",
      +  "type": "string"
      +}
  8. Changed2 schema fields changedv0.39.0
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "checkout",
      -  "form"
      -]New value: +[
      +  "checkout",
      +  "form",
      +  "chrome"
      +]
    • addedInput schema / properties / footer
      Added value: +{
      +  "description": "action:\"chrome\" — build a shared FOOTER instead of a header",
      +  "type": "boolean"
      +}
  9. Addedv0.12.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantial behavior: checkout publishes the page and 404s without all four steps, checkout_sync re-reads methods and republishes, overlay_attach re-reads the page, global_attach/global_detach write the band ROOT reference, template_share sends to org review, and dry run returns the plan. These are meaningful side effects, preconditions, and dependencies that annotations alone do not cover. The mutation actions are consistent with readOnlyHint=false, and the detach/remove actions do not clearly contradict destructiveHint=false.

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

Conciseness3/5

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

The content is relevant and dense, but the description is a single semicolon-heavy paragraph covering fifteen actions, which makes it hard to scan and risks burying per-action requirements. The opening sentence front-loads the fixed-order framing, but the rest is not structured as action-by-action guidance. It is not padded, but its structure limits usability.

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 complex multi-action tool with no output schema, the description supplies ordering rules, action-specific preconditions, side effects, and dry-run behavior. It still leaves gaps around permissions/auth requirements, return values for non-dry-run calls, and the purpose of some parameters and secondary actions such as menu_id-based menu binding. Completeness is therefore strong but not exhaustive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds considerable meaning beyond schema coverage, tying parameters to actions and conditional behavior: kind and list_id for overlay_attach, overlay_id omission creating from seed, global_id omission listing the site's sections, global_kind defaults, footer:true building a footer, settings merge behavior for form, and relocalize targeting existing cart drawers. It explains several conditional and default semantics that the schema does not fully capture. Some parameters such as menu_id, site_id, page_name, and headline remain undocumented, but overall the description substantially compensates for the 65% schema coverage.

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?

The description clearly frames the tool as running ordered store-construction flows and then defines each action with specific verbs and resources, such as publishing checkout pages, seeding form templates, building chrome, attaching overlays, installing apps, and managing shared sections. It is a multi-action bundle rather than a single resource, but an agent can still understand what each action does. Sibling differentiation is partial: it names sb_review for siteChrome and open_cart controls, but does not explicitly compare the tool as a whole against neighboring page/add tools.

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?

The description gives concrete when-to-use guidance for several actions: checkout_sync should run after adding a shipping method or enabling a gateway, global_attach is the answer for a page missing the site header while chrome would wrongly build a second one, and cart is needed before open_cart controls work. It also explains overlay_attach requiring a re-read and app installing pages when needed. Guidance is strong within the actions but lacks an explicit statement of when to select this tool over siblings such as sb_add or sb_page_create.

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