Skip to main content
Glama

Lokand Restaurant MCP

Get site

get_site
Read-onlyIdempotent

Read the business's website: document (the v3 site document — settings, home, pages, and templates[page_id] → sections → blocks, with the ids every other site op needs), theme (what the live theme offers: every section and block type with its settings, the theme settings), resolved_settings (the concrete theme settings the site renders with), live_theme (the custom theme code in use, with its file paths, or null for a system theme), style_hooks (stable [data-lk="…"] attributes custom_css can target on a system theme), system_themes (for set_system_theme) and templates (segment layouts for apply_template). Settings are listed compactly as "id:type(options)"; pass detail: "full" for labels and defaults. ALWAYS call this before changing the site.

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_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNo
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description is not obligated to restate safety. It adds real behavioral context: the mandatory read-before-write workflow, the compact-vs-full encoding tradeoff for settings, and that live_theme is null for a system theme. It says nothing about size limits, pagination, or failure modes on a tool with openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The action statement is front-loaded and the alternative-call warning is the closing sentence, so both anchors land early and late. The middle is one very dense clause per return key, each mapping to a genuine return field, though the long inline enumeration is heavy to parse in a single swallow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the full burden of explaining return values, and it names and characterizes every top-level key. Combined with the detail-parameter behavior and the call-before-mutation rule, an agent has everything needed to invoke and interpret this tool correctly.

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 description coverage is 0%, so the description must carry the load, and it does document the non-obvious `detail` parameter: compact is the default rendering ("id:type(options)") and full adds labels and defaults. `business_id` is left implicit, but it is self-evident from the required string. This compensates well for the coverage gap on only two parameters.

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?

Opens with a specific verb and resource ("Read the business's website") and then enumerates the exact return surface (document, theme, resolved_settings, live_theme, style_hooks, system_themes, templates). An agent can tell this apart from get_business, get_style, or theme_get from the description alone, and the parenthetical explains that document carries the ids every other site op needs.

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?

Gives an explicit, emphatic precondition: "ALWAYS call this before changing the site." It also names which returned fields feed which siblings (system_themes for set_system_theme, templates for apply_template), which is genuine routing guidance. It does not state when-not to use it, nor how it differs from other read tools like get_style or theme_get.

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