Skip to main content
Glama

Lokand Restaurant MCP

Theme get

theme_get
Read-onlyIdempotent

One theme's details and upload status: ready (the version is stored and can be published), processing (poll again in a second or two) or failed (with the error).

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

Input Schema

NameRequiredDescriptionDefault
theme_idYesA theme id from theme_list (or the system theme id lokand-base)
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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the three-state upload lifecycle (ready/processing/failed) and the fact that a failed state carries the error, which tells the agent how to interpret and act on the result.

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?

A single dense sentence that front-loads the resource and then enumerates the status values. Every clause carries information; the parenthetical error note is useful rather than filler.

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?

With no output schema, the description must carry return-value meaning, and it does explain the status field and error case. However, it never says what 'details' comprise or what business_id scopes, leaving a real gap for a two-parameter tool.

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?

Schema coverage is only 50%: theme_id is documented in the schema (including the lokand-base system id), but business_id has no description anywhere. The description text mentions no parameters at all, so it does not compensate for the undocumented business_id.

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 names a specific verb and resource ('One theme's details') and adds the upload-status dimension, which distinguishes it from the list-oriented sibling theme_list. It stops short of explicitly naming an alternative, but the singular scope is unambiguous.

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?

Usage is only implied: the 'poll again in a second or two' note tells the agent this is the tool to re-call while a theme is processing. There is no explicit statement of when to prefer this over theme_list or theme_history, and no prerequisites are given.

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