Skip to main content
Glama

Lokand Restaurant MCP

Delete category

delete_category
Destructive

Delete a menu category (section). Its items are NOT deleted — they stay on the menu without a section; move them with update_item category_id or delete them with delete_item.

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": {
      "category_id": "<category_id>"
    },
    "name": "delete_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
category_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the critical non-obvious consequence: child items survive as sectionless menu entries rather than being cascade-deleted. It stops short of mentioning irreversibility, permission requirements, or what a failed/missing category_id returns.

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 zero filler; the destructive consequence is front-loaded immediately after the action statement, and remediation options follow. Every clause carries information an agent needs before calling.

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 one-parameter destructive tool with no output schema, the description covers the main risk (orphaned items) and the follow-up paths. It lacks prerequisites such as needing a valid category ID or required permissions, but an agent can call it correctly from what is given.

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 0%, so the single required parameter category_id is documented nowhere; the description never names it or states where the ID comes from (e.g., get_menu output). The meaning is inferable from standard conventions, which keeps this at a minimum-viable 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete a menu category (section)" gives a specific verb plus resource and disambiguates the term 'category' with the synonym 'section'. The parentheses and the reference to items remaining clarify exactly which object is removed, distinguishing it from delete_item and delete_menu.

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

Usage Guidelines4/5

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

The description explicitly redirects the agent to alternatives: update_item with category_id to relocate orphaned items, and delete_item to remove them. It does not state when deletion of an entire menu (delete_menu) is preferred, but the guidance given is concrete and actionable.

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