Skip to main content
Glama

Lokand Restaurant MCP

Add category

add_category

Add a category (section) to a menu. Returns the new category_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": {
      "menu_id": "<menu_id>",
      "name": "<name>"
    },
    "name": "add_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional caller-chosen id (8-64 chars). Reuse the same id when retrying so a retry can never create a duplicate.
nameYesCategory name, e.g. "Starters"
menu_idYes
sort_orderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description usefully adds the return value (new category_id), which no output schema provides. However, it says nothing about retry/duplicate behavior, even though the schema's optional id parameter exists specifically for retry safety — a notable omission for a write tool.

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?

Two short sentences, front-loaded with the action and followed by the return value, with no wasted wording. Brevity here borders on under-specification, but the structure itself is clean.

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 mutation tool with half its parameters undocumented and no output schema, the description is thin: it omits prerequisites, the meaning of sort_order, and retry/idempotency guidance that the schema hints at. The return value is the only real addition beyond structured fields.

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

Parameters2/5

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

Schema description coverage is only 50%: menu_id and sort_order carry no schema descriptions, and the description adds no meaning for any parameter. It does not explain menu_id's role, sort_order's default or placement semantics, or how the caller-chosen id interacts with the declared non-idempotent hint.

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?

The description gives a specific verb and resource ("Add a category (section) to a menu") and clarifies the domain term by equating category with section. It also states the immediate effect (returns the new category_id). It does not explicitly contrast with siblings like rename_category or add_section, but the verb+resource pair is unambiguous.

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?

There is no guidance on when to use this versus alternatives such as create_full_menu or import_menu, and no stated prerequisites (e.g. that menu_id must reference an existing menu). The agent must infer call conditions entirely.

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