Skip to main content
Glama

Lokand Restaurant MCP

Publish brand template

publish_brand_template
Destructive

Chains only: make this location's published site the brand template that every linked location of its organization shows (see set_brand_link). Requires brand owner/admin and the franchise 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": {
      "business_id": "<business_id>"
    },
    "name": "publish_brand_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description supplies the reason: the change propagates to every linked location in the organization, which is real blast-radius information an agent cannot get from the annotations. It also adds authorization and plan requirements. It does not say whether an existing brand template is overwritten or how to undo it.

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?

A single sentence with the scope qualifier front-loaded and zero filler. Prerequisites and the sibling reference are packed in without redundancy.

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 one-parameter destructive mutation with no output schema, it covers scope, permissions, plan requirement, propagation target and a sibling pointer. The remaining gaps are the parameter's identity/semantics and what happens to an already-published brand template.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it never mentions business_id. The phrase 'this location's' only loosely implies that business_id identifies the source location; format, whether it must belong to a chain, and whether it must already have a published site are unstated.

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+resource+effect: it makes this location's published site the brand template shown by every linked location. The 'Chains only:' prefix scopes it, and the pointer to set_brand_link separates it from the related linking tool. An agent can tell what it does without opening the schema.

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?

Gives an explicit applicability constraint ('Chains only') and the prerequisites (brand owner/admin, franchise plan), plus a pointer to set_brand_link for the related linking behavior. It does not spell out the inverse case (when not to call it, e.g. single non-franchise locations), so it stops short of full when/when-not guidance.

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