Skip to main content
Glama

Lokand Restaurant MCP

Move section

move_section
Destructive

Move a section to a 0-based position within its page.

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

Input Schema

NameRequiredDescriptionDefault
page_idYesPage id, e.g. home, menu, about, loyalty
positionYes0-based position
section_idYesSection id from get_site
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, which carries most of the safety story. The description only adds the scoping fact that the move stays within the same page; it says nothing about reordering consequences for sibling sections, whether the position is clamped to the existing count, or cross-page moves being disallowed.

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?

One short, front-loaded sentence with no wasted words. It is efficient but borders on under-specified for a four-parameter destructive mutation.

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

Completeness2/5

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

For a destructive, non-idempotent reorder operation with no output schema, the description should explain what shifts, what happens on out-of-range positions, and permission needs. None of that is present; the annotations carry the entire behavioral load.

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 75%, so most parameters are already documented in the schema — including position's own '0-based position' note, which the description merely repeats. The description adds no semantics for business_id, which is undocumented 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?

States a specific verb (Move) and resource (section) plus the target destination (a 0-based position within its page). The resource distinguishes it from move_block, though the description never confirms that separation explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance, no alternatives named, and no exclusions. An agent gets no help deciding between move_section, update_section, and move_block beyond the noun in the name.

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