Skip to main content
Glama

Lokand Restaurant MCP

Theme list

theme_list
Read-onlyIdempotent

List the business's custom themes (id, name, role live|unpublished|development, version, upload status) and the system themes. Custom theme code is a Pro feature.

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": "theme_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The supplied annotations already declare this as a read-only, idempotent, non-destructive operation, so the safety profile is clear. The description adds useful output detail and a Pro-feature note about custom theme code, but it does not explain permissions, pagination, or other behavioral constraints. Given the annotation coverage, this is a reasonable but not rich behavioral disclosure.

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 description is compact and front-loads the listing purpose, followed by the returned fields and a short feature note. It contains little waste, though the Pro-feature sentence is somewhat tangential to the core listing operation.

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?

For a simple one-parameter list tool with rich annotations but no output schema, the description provides the essential purpose and returned fields. It is still incomplete around the required business_id parameter and when this tool should be chosen over sibling theme tools. The definition is usable but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, business_id, and the schema description coverage is 0%. The description says 'business's' but does not explain what business_id is, how to obtain it, or any format expectations. With low schema coverage, the description should compensate, but it does not add meaning beyond the parameter name.

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 verb and resource: list the business's custom and system themes. It also names the returned fields (id, name, role, version, upload status), making the scope clear. It does not explicitly distinguish itself from siblings such as theme_get, but the purpose is still clear.

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 implies usage for obtaining a theme overview and identifies custom versus system themes. It does not explicitly say when to use this instead of theme_get or other theme operations, nor does it state prerequisites such as needing a valid business_id. The implied context is adequate but not strong guidance.

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