Skip to main content
Glama

Lokand Restaurant MCP

Get storefront context

get_storefront_context
Read-onlyIdempotent

The exact data a theme renders with (the StorefrontData Liquid objects are built from): the business (localized, brand site applied), every active menu with items, primary menu id, loyalty/ordering flags, the stamp-card program and its resolved style — plus theme_data (the site document) and live_theme. Use it to preview or test theme code locally.

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

Input Schema

NameRequiredDescriptionDefault
localeNoDefaults to the business's default locale
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description's added value is payload scope, which it delivers well: read-only snapshot of exactly what a theme renders. It does not mention payload size, cost, or whether output is cached/live, which is meaningful for an openWorldHint read.

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?

Front-loaded with the payload overview in one dense sentence, followed by a single purpose sentence. No filler, no repetition of the name or title.

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?

No output schema exists, so the enumerated payload list does useful work compensating, but the shape of theme_data/live_theme and the size/format of the response stay unstated. Guidance on the required business_id is also absent.

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%: locale is documented in the schema, business_id has no description. The description adds no clarification of business_id or the locale fallback, so the undocumented required parameter remains unexplained.

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?

States a specific verb+resource (get_storefront_context) and enumerates the payload: business, menus, flags, stamp-card program, theme_data and live_theme. It distinguishes itself from get_menu/get_site by claiming the full rendering payload, though it never names those siblings 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?

Offers one use case: 'Use it to preview or test theme code locally.' There is no guidance on when to prefer get_menu, get_site, or theme_get instead, and no note on prerequisites such as needing a published theme or an existing business.

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