Skip to main content
Glama

Lokand Restaurant MCP

Import menu

import_menu

Start an AI import of a restaurant's menu from the URL of its existing website. Returns an import_id to poll with import_status; when complete, call commit_import to turn the draft into a real menu.

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>",
      "url": "<url>"
    },
    "name": "import_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL of the site to import the menu from
business_idYes

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 non-read-only, non-idempotent, open-world, non-destructive behavior. The description adds the key behavioral fact those annotations cannot convey: this is asynchronous and only produces a draft, which stays unreal until commit_import is called. It omits failure modes, whether drafts expire, and any auth or rate-limit constraints, so it stops 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?

Two sentences, zero filler. The action and source come first, then the downstream workflow, which is the right order for an agent deciding whether to call it.

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?

No output schema exists, yet the description names the return value (import_id) and its purpose, and it closes the loop through commit_import. What remains unstated is what happens on an unreachable or non-menu URL, and the meaning of the undocumented business_id parameter.

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 50%: url is documented in the schema, business_id is not. The description reinforces that the URL must be the site's existing public website, which helps, but it never explains what business_id identifies or that the imported menu is attached to that business. Partial compensation for a partial 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?

States a specific verb (start an AI import) plus the resource (a restaurant's menu) and the source (URL of its existing website). It also distinguishes itself from the two workflow siblings, import_status and commit_import, so an agent can place it in the pipeline without opening any schema.

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?

Explicitly prescribes the sequence: call this first, poll with import_status using the returned import_id, then call commit_import once complete. That is both when-to-use and which-alternative guidance, with the condition for each handoff spelled out.

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