Skip to main content
Glama

Lokand Restaurant MCP

Theme upload

theme_upload
Destructive

Upload a complete custom theme (Pro plan) as a new commit in its Git repo. Files are validated and compiled at once — a 422 lists every problem as path: message lines — then compiled in the background: poll theme_get until status is ready, then theme_publish. Without theme_id, role development reuses your one development theme and role unpublished creates a new theme; with theme_id it stores the next version of that theme. Updating the live theme needs allow_live: true.

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": {
      "business_id": "<business_id>",
      "files": "<files>"
    },
    "name": "theme_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
roleNodevelopment = your private work-in-progress theme (one per user, replaced on each upload); unpublished = a saved theme ready to publishdevelopment
filesYesTheme files by path, e.g. {"sections/hero.liquid": "...", "config/settings_schema.json": "..."}
messageNoCommit message
theme_idNoA theme id from theme_list (or the system theme id lokand-base)
allow_liveNoWith the live theme's id: update the live site in place
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / theme_id / description
      Previous value: -"A theme id from theme_list (or a system theme id: lokand-base, lokand-one)"New value: +"A theme id from theme_list (or the system theme id lokand-base)"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructive, non-idempotent and open-world, so the description's job is to explain what gets destroyed and how failures surface. It does: files are validated/compiled at once with a 422 listing every problem as 'path: message', compilation continues in the background, and dev-theme uploads overwrite the previous version. It stops short of describing the success response, but the mutation semantics are unusually well disclosed.

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?

Three dense sentences with zero filler, front-loading what the tool does before the branch conditions and preconditions. It is tightly packed — the role/theme_id branching sentence carries several conditions at once — but nothing is redundant.

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 7-parameter, nested-file, destructive, asynchronous mutation with no output schema, the description covers validation, failure format, background compilation, polling, and live-site gating. The only notable gap is what a successful call returns (commit/version identifier), which an agent may need before polling.

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?

Adds behavioral meaning to parameters that the 71%-coverage schema only partly documents: role is explained as 'one per user, replaced on each upload' vs 'saved theme ready to publish', theme_id as 'stores the next version of that theme', and allow_live as the gate for in-place live updates. This is real guidance an agent could not infer from the schema alone.

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?

States a specific verb and resource — 'Upload a complete custom theme (Pro plan) as a new commit in its Git repo' — which immediately separates it from theme_write_files, theme_sync and update_theme by scope (whole theme, new commit). It also names workflow siblings (theme_get, theme_publish) so the agent knows where this fits.

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?

Gives explicit branching rules: no theme_id + role development replaces the single dev theme, role unpublished creates a new theme, with theme_id it stores the next version; and it states the exact prerequisite for touching the live site (allow_live: true). It also prescribes the follow-up sequence — poll theme_get until ready, then theme_publish.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources