Skip to main content
Glama

Lokand Restaurant MCP

Theme pull

theme_pull
Read-onlyIdempotent

Download a theme's files ({path: text}). theme_id "lokand-base" returns the system theme to start from. Custom themes return their latest stored version. A whole theme is large: pass search to find the lines you need to change, or list_only for paths and sizes, then paths for whole files.

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

Input Schema

NameRequiredDescriptionDefault
pathsNoReturn only these files
searchNoCase-insensitive text to find, e.g. ".menu-item .name"; returns matching lines as {path, line, text} instead of files (combine with paths to limit where it looks)
theme_idYesA theme id from theme_list (or the system theme id lokand-base)
list_onlyNoReturn only {path, size} for every file
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / theme_id / description
      Previous value: -"A theme id from theme_list (or a system theme id: lokand-base, lokand-one)"New value: +"A theme id from theme_list (or the system theme id lokand-base)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds real value on top: lokand-base returns the system theme, custom themes return their latest stored version, and full-theme downloads are large so partial modes are recommended. Missing are any size/response limits or truncation behavior for large result sets.

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?

Front-loaded with the purpose and return shape, then the special theme_id case, then the size-driven mode advice — a logical order with no filler. Minor blemishes: an unbalanced quote in 'theme_id "lokand-base' and a slightly compressed final sentence listing three modes.

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?

With no output schema, the description still documents all three return shapes ({path: text}, {path, line, text}, {path, size}) and the special theme_id behavior, which is what an agent needs to call this correctly. The only remaining unknown is any cap on very large whole-theme responses.

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 description coverage is 80%, so the schema already explains paths, search, list_only, and theme_id, including the {path, line, text} return shape. The description reinforces the workflow ordering (list_only, then paths) and which theme_id value is special, but adds little syntax or format detail beyond the schema.

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 and resource ('Download a theme's files') and immediately pins the return shape as {path: text}, plus clarifies the special lokand-base id versus custom themes. It does not distinguish itself from close siblings such as theme_get or theme_write_files, so it falls 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?

Gives unusually concrete mode-selection guidance: use search for the lines you need to change, list_only for paths and sizes, and paths for whole files, motivated by 'a whole theme is large'. It stops short of explicit when-not-to-use or sibling-tool routing (e.g., when to prefer 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