Skip to main content
Glama

Lokand Restaurant MCP

Add section

add_section
Destructive

Add a section of a given type (keys of get_site.theme.sections) to a page, optionally from one of its presets, with a settings patch and a 0-based position (default: the end). Sections hold blocks; add them with add_block.

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

Input Schema

NameRequiredDescriptionDefault
kindNoAlias of type
typeNoSection type from get_site
presetNoStart from one of the 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.
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this as a non-idempotent, destructive, open-world write, so the safety profile is covered. The description adds the useful default-position behavior and the section/block relationship, but says nothing about permissions, whether settings patch is merged destructively, or what happens if position exceeds the list length.

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 sentences, verb-fronted, with no filler; the parenthetical domain hint sits right after the parameter it constrains. The single dense first sentence packs several clauses, but each carries information.

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 a 7-parameter destructive mutation with a nested settings object and no output schema, the description covers inputs well but never addresses what comes back (e.g., the new section's id/handle) that the agent would need before calling add_block, nor failure modes.

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 86%, so the schema already documents type, preset, position, and the JSON-merge-patch semantics of settings. The only genuinely additive hint is pointing at get_site.theme.sections as the source of valid type keys; the rest restates schema text, so baseline 3 is appropriate.

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?

The description uses a specific verb and resource ('Add a section ... to a page') and explicitly bounds the input domain ('type (keys of get_site.theme.sections)'). It also distinguishes itself from the nearest sibling by noting 'Sections hold blocks; add them with add_block.'

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?

It gives clear operating context: sections are added to a page, blocks go through add_block instead, and omitting position appends at the end. It stops short of explicit when-not conditions or prerequisites (e.g., page must exist, section limits).

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