Skip to main content
Glama

Lokand Restaurant MCP

List menus

list_menus
Read-onlyIdempotent

List the active menus of a public Lokand restaurant by its slug.

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": {
      "slug": "<slug>"
    },
    "name": "list_menus"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe business's public slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value by noting results are limited to "active" menus of a "public" restaurant, which explains why some menus may be absent. It says nothing about pagination, ordering, or result size, which is the main remaining behavioral 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?

One sentence, front-loaded with the action and resource, with the scope qualifier following immediately. Every word contributes; there is no boilerplate or repetition of the title.

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 simple single-parameter read tool with rich annotations and a fully documented schema, the description covers the essentials of what is returned (active menus of a public restaurant). The only shortfall is the absence of any note on result shape or pagination, which matters mildly for a list endpoint with no output schema.

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 a single parameter with 100% schema coverage, so the schema already explains that slug is "The business's public slug". The phrase "by its slug" in the description merely restates this and adds no format, casing, or validation detail beyond the schema. Baseline 3 applies when the schema carries the parameter semantics.

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 ("List the active menus") plus a clear scope qualifier ("of a public Lokand restaurant"). An agent can tell this is the collection-level read, distinct from a single-menu fetch like get_menu, though the description never names any sibling explicitly.

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 only implied: the agent gathers that it needs a public restaurant slug and that it should use this to enumerate menus. There is no explicit when-to-use versus get_menu or list_businesses, and no stated preconditions (e.g., whether the restaurant must be claimed or published).

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