Skip to main content
Glama

Lokand Restaurant MCP

Reorder items

reorder_items
Destructive

Set the order of the items in one section of a menu. List item ids top to bottom; listed items from another section are moved into this one, and the section's other items keep their relative order after the listed ones.

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": {
      "menu_id": "<menu_id>",
      "category_id": "<category_id>",
      "item_ids": "<item_ids>"
    },
    "name": "reorder_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
menu_idYes
item_idsYes
category_idYesThe section being ordered; null = items without a section

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses a genuinely non-obvious side effect: items from other sections get moved into this one, and unlisted items retain relative order after the listed ones. It does not address failure modes, whether the list must be exhaustive, or permission requirements.

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 sentences, zero waste, with the core action front-loaded and the edge-case semantics in the second sentence. Nothing needs trimming.

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

Completeness5/5

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

For a 3-parameter destructive mutation with no output schema, the description covers the ordering contract and the cross-section move behavior that an agent could not infer. Remaining gaps (error handling, permissions) are minor.

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 only 33% (only category_id is documented), so the description must compensate — and it does for item_ids by specifying the array is ordered top-to-bottom. menu_id is self-evident, but the 500-item cap and category_id's null semantics are left to the schema.

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 and resource with scope: "Set the order of the items in one section of a menu." That is clearly distinguishable from the sibling reorder_categories, though the description never names that sibling explicitly.

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?

Usage is implied by the scope sentence (use when you want to set item order within a section), but there is no explicit when-to-use/when-not guidance and no named alternative for reordering categories or featured items.

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