Skip to main content
Glama

Lokand Restaurant MCP

Update block

update_block
Destructive

Merge-patch one block's settings (null removes a key) and/or hide/show it.

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>",
      "page_id": "<page_id>",
      "section_id": "<section_id>",
      "block_id": "<block_id>"
    },
    "name": "update_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenNo
page_idYesPage id, e.g. home, menu, about, loyalty
block_idYesBlock id from get_site
settingsNoSettings as a JSON merge patch (null removes a key). get_site lists each type's settings.
section_idYesSection id from get_site
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive, openWorld, and non-idempotent behavior. The description adds useful semantics beyond that by explaining merge-patch behavior and specifically that null removes a key, which is important context for a destructive mutation.

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?

The description is a single front-loaded sentence that states the operation, the key merge-patch nuance, and the visibility toggle without wasted wording.

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 mutation tool with rich annotations and schema descriptions for most parameters, the description covers the core operation and important null-removal behavior. It could say more about live-site effects of hidden and block-type-specific settings, but the essential contract is present.

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 67%, and the schema already describes settings as a JSON merge patch with null removing a key. The description restates that behavior and maps hide/show to the hidden parameter but does not add meaning for business_id, page_id, section_id, or block_id.

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 states a specific verb and resource: merge-patching one block's settings and toggling its visibility. It is clear enough to distinguish from add_block, move_block, and remove_block, but it does not explicitly name or contrast with those siblings.

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?

The description implies when to use it: updating block settings and hiding/showing a block. It gives no explicit exclusions or guidance on when to prefer move_block, remove_block, or update_section instead.

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