Skip to main content
Glama

Lokand Restaurant MCP

Create menu

create_menu

Create an EMPTY menu on a business the caller manages (add sections with add_category, dishes with add_item). For a whole menu at once, use create_full_menu instead. Returns the new menu_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": {
      "business_id": "<business_id>",
      "name": "<name>"
    },
    "name": "create_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional caller-chosen id (8-64 chars). Reuse the same id when retrying so a retry can never create a duplicate.
nameYesMenu name, e.g. "Dinner"
is_activeNoWhether the menu is live on the public site
business_idYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the created menu is empty, it requires a business the caller manages (permission scope), and it returns the new menu_id. It does not discuss failure modes or rollback, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the core action and the EMPTY qualifier, then alternatives, then the return value. No filler and nothing that could be moved to a more useful position.

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?

With no output schema, the description usefully states the return value (menu_id), and it covers the permission boundary and sibling alternatives for a straightforward create tool. The only real gap is the undocumented optional fields, which the schema mostly handles on its own.

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 60%, with business_id and description left undocumented in the schema. The phrase "a business the caller manages" does add permission semantics for business_id, but nothing in the description clarifies the optional description field or the is_active default. Adequate but not compensating for the coverage gap.

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?

"Create an EMPTY menu on a business the caller manages" gives a specific verb, resource, and — critically — a scope qualifier (EMPTY) that distinguishes it from the bulk sibling create_full_menu. The parenthetical naming add_category and add_item shows exactly how the empty menu is subsequently populated.

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

Usage Guidelines5/5

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

Explicit routing is provided in both directions: use add_category/add_item to build on an empty menu, and use create_full_menu instead when a whole menu is needed at once. An agent can choose between the three create paths without opening any schema.

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