Skip to main content
Glama

Lokand Restaurant MCP

Add block

add_block
Destructive

Add a block (a repeatable piece inside a section: a link, a photo, a testimonial, …) of a type the section accepts (get_site.theme.sections[type].blocks). Nest it in another block with parent_block_id.

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

Input Schema

NameRequiredDescriptionDefault
typeYesBlock type the section accepts (see get_site)
presetNoStart from one of the block type's presets
page_idYesPage id, e.g. home, menu, about, loyalty
positionNo0-based position
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
parent_block_idNoNest inside this block instead of the section

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the write/safety profile is covered. The description adds the useful prerequisite that the type must be accepted by the section and the nesting option, but says nothing about what happens on invalid type, whether position shifts existing blocks, or what the call returns.

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?

A single dense sentence plus a short imperative, with the resource definition and the type constraint front-loaded. No filler, though the parenthetical example list is slightly verbose for the information it carries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with a free-form nested settings object and no output schema, the definition covers the key prerequisite (valid type from get_site) but leaves out ordering behavior, failure modes, and any indication of what is returned. Adequate but with clear gaps given the tool's complexity.

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 88%, so nearly every parameter is already documented, including the settings merge-patch semantics and parent_block_id. The description reinforces type validity against the theme schema and clarifies that parent_block_id nests rather than appends to the section, which is marginal added value over the schema baseline.

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 ('Add') and resource ('block'), then defines the resource precisely as 'a repeatable piece inside a section: a link, a photo, a testimonial'. It also situates blocks relative to sections, so an agent can distinguish this from add_section or add_item 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 Guidelines3/5

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

Implies the precondition that the block type must be one the section accepts, and points at the authoritative source (get_site.theme.sections[type].blocks). However, it never states when to prefer this over siblings like add_section, update_block, or move_block, and gives no explicit 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