Skip to main content
Glama

Lokand Restaurant MCP

Set brand link

set_brand_link
Destructive

Chains only: link this location to its brand's shared site (linked=true) so it shows the brand template's pages and theme, or unlink it (linked=false) to use its own site again. Hours, address, menus and ordering always stay this location's own. The brand template is set with publish_brand_template.

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

Input Schema

NameRequiredDescriptionDefault
linkedYestrue = show the brand's shared site here; false = this location's own site
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, and the description adds real value on top: it explains that linking swaps in the brand template's pages and theme while hours, address, menus and ordering remain local. It does not say what happens to location-specific edits made under the brand template when unlinking, which is the destructive loss an agent most needs to warn about.

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 'Chains only' precondition, then the two boolean outcomes, then the reassurance about unaffected data fields. No redundancy or hedging.

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 two-parameter mutation with no output schema and informative annotations, this is nearly complete: precondition, both outcomes, side-effect boundary, and the related setup tool are all present. The only gap is the unlink data-loss scenario and any account/plan requirement implied by 'Chains only'.

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 description coverage is only 50% — 'linked' is documented in the schema and restated in the description, but 'business_id' appears in neither. The boolean semantics are well covered; the identifier parameter is left to the name 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 (link/unlink this location to its brand's shared site) plus the scope constraint 'Chains only' and the exact effect on both boolean values. This is clearly distinguishable from template-related siblings like publish_brand_template, which the description even names as the tool that sets the template.

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?

Explicitly maps linked=true to 'show the brand's shared site' and linked=false to 'use its own site again', and says the template itself is set with publish_brand_template. It gives no explicit when-not-to-use case beyond the 'Chains only' scope, which keeps it short of a 5.

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