Skip to main content
Glama

Lokand Restaurant MCP

Move block

move_block
Destructive

Move a block to a 0-based position among its siblings.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 safety profile is covered. The description adds that the position is scoped to siblings, but says nothing about what happens to the displaced blocks, whether the section must already exist, or the effect on ordering elsewhere.

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?

A single front-loaded sentence with no redundant wording. Every clause—verb, resource, index semantics, sibling scope—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 destructive, non-idempotent mutation with five required parameters and no output schema, the description is thin. The annotations cover the safety warning and the schema covers most parameters, but the description never explains the outcome of a move or any failure conditions.

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 80%, so position, page_id, block_id, and section_id are already documented inline. The phrase "among its siblings" reinforces that position is relative to blocks within the target section, which is a modest clarification over the schema's "0-based position."

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?

"Move a block to a 0-based position among its siblings" gives a specific verb (move), resource (block), and scope (sibling ordering), which is enough to distinguish it from reordering a section. It stops short of naming siblings like update_block or move_section, so sibling differentiation is left implicit.

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?

The description states what the tool does but gives no when-to-use guidance, no prerequisites, and no indication of when to prefer update_block or move_section instead. An agent must infer the reordering use case purely from the verb.

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