Skip to main content
Glama

Lokand Restaurant MCP

Import status

import_status
Read-onlyIdempotent

Check an AI menu import: processing, complete (draft ready to commit), or failed. progress.found lists what is known so far; complete responses include the draft for review.

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": "import_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
import_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description earns credit for adding what the annotations cannot: the three possible lifecycle states and the meaning of the `progress.found` field for partial results. It does not cover polling cadence, eventual-consistency behavior, or error handling, which is a modest gap.

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, and the outcome states are front-loaded before the return-value detail. Every clause carries information an agent would otherwise have to guess.

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 carries the burden of describing returns, and it does so reasonably: states, partial-progress content, and inclusion of the draft on completion. Missing are any note on how long processing typically takes or what to do on failure, but the core is covered.

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?

There is one required parameter, `import_id`, and schema coverage is 0%, so the schema documents only type and minLength. The description implies the id refers to an AI menu import but adds no format, source, or retrieval guidance for obtaining it. With a single obvious identifier, the omission is minor but not fully compensated.

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 ('Check an AI menu import') and enumerates the outcome states (processing, complete, failed), so an agent knows exactly what it returns. It does not explicitly distinguish itself from siblings like commit_import or claim_status, which keeps it short of a 5.

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?

Usage is implied by the wording: you poll this after kicking off an import, and 'complete (draft ready to commit)' hints that commit_import is the follow-up step. However, there is no explicit when-to-use guidance, no polling/repeat guidance, and no named alternative for cases where this is the wrong tool.

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