Skip to main content
Glama

Lokand Restaurant MCP

Theme publish

theme_publish
Destructive

Make a custom theme the live site's code (Pro plan). The previous live theme becomes unpublished and cached pages refresh. warnings lists parts of the current site document the new theme doesn't define (fix them with the site ops).

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>",
      "theme_id": "<theme_id>"
    },
    "name": "theme_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYesA theme id from theme_list (or the system theme id lokand-base)
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

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description still adds value: it discloses the state transition (the previous live theme becomes unpublished, cached pages refresh) and explains the returned `warnings` field listing site-document parts the new theme lacks. It stops short of stating irreversibility or rollback options, which would have made it a 5.

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?

Three tight sentences, front-loaded with the action, then side effects, then the return-value caveat. No filler and nothing is buried.

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 2-parameter destructive mutation with no output schema, the definition covers the plan prerequisite, the side effects on the prior theme and caches, and the meaning of the `warnings` response. Only the recovery path after publishing remains unstated.

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 coverage is 50%: theme_id is documented (including the lokand-base system id) while business_id is bare. The description only indirectly reinforces that theme_id must be a custom theme; it adds no format or constraint detail for business_id, so it stays at the schema-driven baseline.

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 concrete verb+resource: making a custom theme the live site's code, plus the plan gate (Pro). It clearly distinguishes publishing from merely setting/updating a theme, though it never names a sibling such as set_theme or theme_unpublish to draw the boundary explicitly.

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

Usage Guidelines3/5

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

Usage context is implied by 'custom theme' and the Pro plan prerequisite, and the follow-up hint ('fix them with the site ops') points at remediation. But there is no explicit when-to-use vs theme_unpublish/set_theme, and no statement about whether this can be undone.

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