Skip to main content
Glama

Lokand Restaurant MCP

Commit import

commit_import

Commit a completed AI menu import as a real menu (creates the menu, categories, and items). 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": {
      "import_id": "<import_id>"
    },
    "name": "commit_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
import_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already disclose that this is not read-only, is open-world, and is not idempotent. The description usefully adds that it creates a menu plus categories and items, and returns the new menu_id, but it does not discuss permissions, whether repeated calls duplicate data, or failure/partial-creation behavior.

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?

The description is two concise clauses, front-loaded with the core action and followed by the concrete side effects and return value. Every sentence carries useful information without padding.

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

Completeness3/5

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

For a one-parameter mutation tool with no output schema, the description covers the main effect and return value, which is helpful. However, it leaves the required import_id parameter undefined and omits operational context such as idempotency implications and what happens if the import is not actually complete.

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?

There is one required import_id parameter with 0% schema description coverage, and the description does not explain what an import_id is, where it comes from, or its expected format. Mentioning 'completed AI menu import' only loosely implies the parameter's purpose.

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 states a specific action and outcome: committing a completed AI menu import into a real menu, including creation of menu, categories, and items. It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools such as import_menu or create_menu.

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 phrase 'completed AI menu import' implies this should be used after an import has finished, but there is no explicit when-to-use guidance, prerequisite check, or comparison with alternatives like import_status.

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