Skip to main content
Glama

Lokand Restaurant MCP

Reorder categories

reorder_categories
Destructive

Set the order of a menu's categories (sections). List category ids top to bottom; any you leave out keep their current 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_ids": "<category_ids>"
    },
    "name": "reorder_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
menu_idYes
category_idsYes

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 declare the mutation profile (readOnlyHint=false, destructiveHint=true), so the description's real contribution is the partial-update rule: omitted categories retain their relative order after the listed ones. That is genuine semantics an agent cannot get from the annotations. It stops short of saying whether the previous full order is lost or how invalid/foreign ids are handled.

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 short sentences with no filler; the core action is front-loaded and the omission rule follows immediately as supporting detail.

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 two-parameter destructive mutation with no output schema, the description covers the action and the most error-prone part of the input semantics. Missing pieces are permission/authorization notes, the 200-id limit, and error behavior for unknown categories.

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?

With 0% schema description coverage, the description carries the burden and does explain category_ids meaningfully: list top to bottom, and omissions are appended in existing relative order. menu_id is left unexplained and the maxItems=200 cap is not surfaced, so it is not fully compensating.

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?

"Set the order of a menu's categories (sections)" gives a specific verb plus resource and even glosses "categories" as "sections" so the agent knows the target object. It does not explicitly distinguish itself from the sibling reorder_items, so it falls short of a 5.

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 scope (a single menu's category ordering) implies when the tool applies, but there is no explicit when-to-use guidance, no mention of the sibling reorder_items for item-level ordering, and no stated prerequisites such as the menu existing or category ids being valid.

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