Skip to main content
Glama

Lokand Restaurant MCP

Get style

get_style
Read-onlyIdempotent

Compile one look from the style library into the exact settings to send in ONE update_theme_settings call (palette, fonts, shape, spacing and a signature custom_css on the stable [data-lk] hooks), plus the menu section style to set, the photo to put in the home hero (hero_image, if any), how to shape the home page, the copy voice, and do / don't lists. By default it uses the logo's color when the logo has a strong one. level: safe, distinct or bold (from suggest_styles, or the owner's ask: 'bolder' / 'simpler').

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

Input Schema

NameRequiredDescriptionDefault
levelNo
styleYes
seed_colorNoLead color to build the palette from, e.g. the owner's brand color
business_idYes
use_logo_colorsNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds real behavioral context on top, notably that the palette is derived from the logo's color when the logo has a strong one. It is also clear that this is a pure compile step with no side effects, and it discloses the shape of the returned guidance. It stops short of saying what happens when no style or logo is available, which keeps it from 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the first sentence is a single sprawling clause string of eight-plus list items followed by a second sentence that re-introduces `level`. The content largely earns its place, but the run-on packing makes it harder to parse than a short bulleted breakdown of inputs and outputs would be.

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?

There is no output schema, so the description must describe what comes back, and it does: palette, fonts, shape, spacing, custom_css on [data-lk] hooks, menu section style, hero_image, home page shaping, copy voice, and do/don't lists. The main omission is that it never states what happens if the business has no site/theme yet, or that `style` should normally be sourced from suggest_styles rather than invented.

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?

Schema coverage is only 40%, so the description must carry weight, and it does for the two undocumented parameters: it explains what `level` means (safe / distinct / bold) and where its value comes from, and it explains the default color behavior that governs `use_logo_colors`. The `style` enum's fourteen values and `business_id` remain uninterpreted in the description, which is the remaining 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 and output: 'Compile one look from the style library into the exact settings to send in ONE update_theme_settings call', then enumerates the artifacts produced (palette, fonts, shape, spacing, custom_css, menu section style, hero_image, copy voice, do/don't lists). This lets an agent distinguish it from the adjacent suggest_styles (which only picks a style) and update_theme_settings (which consumes the result) 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 Guidelines3/5

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

The description embeds a workflow hint by naming update_theme_settings as the downstream consumer and by tying the level value to suggest_styles or to an owner's phrasing ('bolder' / 'simpler'). However, it never explicitly says when to choose this over apply_style_preset or apply_site_preset, nor whether it must be called before or after suggest_styles, so the guidance is implied rather than stated.

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