Skip to main content
Glama

Lokand Restaurant MCP

Theme git access

theme_git_access
Read-onlyIdempotent

Git access to a custom theme's code: the HTTPS remote and a repo-scoped token (read, or write on the Pro plan). Pushes to main compile automatically and, for the live theme, publish once compiled; theme_get shows a push that failed to compile as push_error. Tokens expire (default 1 hour).

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

Input Schema

NameRequiredDescriptionDefault
scopeNoread
theme_idYesA theme id from theme_list (or the system theme id lokand-base)
business_idYes
ttl_secondsNo

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

A3.7/5.0
Behavior4/5

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

Beyond the annotations it discloses non-obvious traits: tokens expire with a 1-hour default, write scope requires the Pro plan, and failed compiles surface as push_error via theme_get. Those are exactly the operational facts an agent needs. It omits revocation behavior, whether the token is per-theme or per-business, and what error is returned when write scope is requested without Pro.

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?

Three dense sentences, front-loaded with what the tool returns before moving to consequences and expiry. Every clause carries information; the only cost is that the compile/publish sentence is tightly compressed and could be misread as this tool's own side effect.

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?

With no output schema, the description usefully names the two return artifacts (HTTPS remote and repo-scoped token), and it explains downstream behavior for a token that grants write access. For four parameters and a credential-issuing tool this is nearly sufficient; the undocumented business_id and TTL bounds are the remaining gap.

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 only 25%, with business_id undocumented anywhere. The description partially compensates: it explains the read/write distinction and plan constraint for `scope`, and supplies the 1-hour default for `ttl_seconds` that the schema itself does not declare. It says nothing about the ttl_seconds maximum of 604800 or the accepted theme_id sources beyond what the schema already states.

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 states a specific resource and its output precisely: 'Git access to a custom theme's code: the HTTPS remote and a repo-scoped token'. An agent immediately knows this is a credential/remote-provisioning tool rather than a file-editing one, which separates it from theme_pull, theme_write_files, and theme_publish. It does not explicitly name any sibling for contrast, so it stops 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 Guidelines3/5

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

The context for use is implied rather than stated: an agent must infer that this is for git-based workflows instead of theme_pull/theme_sync/theme_write_files. It gives useful operational rules (pushes to main compile, live theme publishes after compile) but never says 'use this instead of X when Y' or lists prerequisites such as plan requirements for write scope.

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