Skip to main content
Glama

Lokand Restaurant MCP

Get started

get_started
Read-onlyIdempotent

How to use Lokand as an agent: the recipes for creating a restaurant for a customer, editing menus, and handing over ownership. Call this first if you're unsure what to do.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_started"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint, idempotentHint, and openWorldHint already tell the agent this is a safe, repeatable read. The description adds that the payload is procedural guidance rather than tenant data, which is genuine value. However, with no output schema, it never says what the recipes look like or how large the response is, so the return shape remains undisclosed.

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 topic is front-loaded, the covered recipes are enumerated compactly, and the actionable call condition comes last where an agent scanning for guidance will still hit 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?

For a zero-parameter, no-output-schema documentation tool this covers what the agent needs in order to decide to call it and what to expect from the content. It could be slightly stronger by noting whether the recipes are returned as static text or generated from the live account state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema baseline is 4 and there is nothing further the description could add. The description correctly does not waste words on parameters and instead spends its budget on content.

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 resource and content type: agent-facing recipes covering restaurant creation, menu editing, and ownership handover. That is far more informative than the tautological title 'Get started'. It does not explicitly contrast itself with siblings like create_restaurant or create_full_menu, so it stops 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 Guidelines4/5

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

'Call this first if you're unsure what to do' gives an explicit trigger condition and a precedence hint over the mutation siblings. It lacks a when-not-to-use clause (e.g., don't call if you already know the exact mutation tool), so it is clear context rather than full routing guidance.

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