Skip to main content
Glama

Lokand Restaurant MCP

Theme unpublish

theme_unpublish
Destructive

Stop using custom theme code: the site goes back to its system theme. The custom theme is kept as unpublished.

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

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's key contribution is the retention fact: the custom theme is kept, not destroyed by the revert. That materially softens the 'destructive' framing in a way annotations alone do not convey. It still omits permissions or what happens to in-flight site state.

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?

Two short sentences, effect stated first and the retention caveat immediately after, with no filler. The phrase 'kept as unpublished' is slightly awkward but conveys the important nuance.

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 single-parameter mutation tool with annotations and no output schema, the description covers the main behavioral consequences: the site reverts and the theme is preserved. Only the parameter's meaning and any permission prerequisities are left unaddressed.

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

Parameters2/5

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

There is one required parameter, business_id, with 0% schema description coverage, and the description says nothing about it. With coverage this low the description is expected to compensate, and it does not, leaving the sole parameter defined only by its name and type.

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 names a specific action (stop using custom theme code) and its concrete effect (site reverts to the system theme), and clarifies that the custom theme survives as unpublished. That distinguishes it in substance from a delete, though it does not name any sibling such as theme_delete or set_system_theme 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 is only implied: an agent can infer this is the right tool when the goal is to revert to the system theme while retaining the custom theme. There is no explicit when-to-use/when-not statement and no named alternative for permanent removal.

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