Skip to main content
Glama

Lokand Restaurant MCP

Update section

update_section
Destructive

Change one section: merge-patch its settings (null removes a key; settings: null resets them all) and/or hide/show it. Ids come from get_site.document.templates[page_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>"
    },
    "name": "update_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenNo
page_idYesPage id, e.g. home, menu, about, loyalty
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.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description earns credit for making the destruction concrete: null removes a key and settings:null wipes all settings. It stops short of permissions/response shape, which keeps it at 4 rather than 5.

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?

Two dense sentences with zero filler; the mutation semantics are front-loaded ahead of the id-source pointer. Parentheticals are used efficiently to carry the destructive edge cases.

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 destructive 5-parameter mutation tool with no output schema, the description covers the operation, the patch semantics, the reset hazard, and the id provenance. The remaining gap is business_id and any auth/permission expectations, which a caller might still need.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, so the description must compensate on the un-instrumented fields. It does: it explains merge-patch semantics for settings, states that settings:null resets everything (beyond what the schema says) and explains what hide/show means for the hidden flag; only business_id remains unaddressed in both places.

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?

"Change one section: merge-patch its settings ... and/or hide/show it" gives a specific verb (change) and resource (section), plus the two mutable facets. It implicitly distinguishes itself from structural siblings like add_section/move_section/remove_section, though it doesn't call them out by name.

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 tells the agent where ids come from (get_site.document.templates[page_id]), which is a real precondition, so usage is more than implied. But it gives no explicit when-to-use guidance, no exclusions (e.g. 'use move_section for reordering'), and no warning about the destructive reset path beyond the parenthetical.

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