Skip to main content
Glama

Lokand Restaurant MCP

Update loyalty card

update_loyalty_card
Destructive

Set up or change the business's loyalty stamp card: how many stamps earn the reward, the reward text, whether the card is live, and its look. Only provided fields change; the first call must include stamps_required and reward_text. Requires the Pro plan (402 plan_required otherwise — offer create_checkout_link).

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

Input Schema

NameRequiredDescriptionDefault
is_activeNoWhether diners can join and collect stamps
business_idYes
card_configNoThe card's look — colors{cardBg,cardFg,stampFilled,stampEmpty}, stampIcon, headline, subline. Replaces the whole style; null resets it to match the site theme.
reward_textNoWhat the guest gets, e.g. "A free coffee"
stamps_requiredNoStamps needed for one reward (2-30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-structured behavior: merge semantics for omitted fields, a first-call field requirement, and the 402 plan-gating error with a prescribed next action. It stops short of explaining what the destructive flag means in practice (e.g., that supplying card_config overwrites the entire existing style), leaving that to the schema.

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

Conciseness5/5

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

Three sentences, all load-bearing: capability first, mutation semantics second, prerequisite and error handling last. No repetition of the title, no filler, and the most decision-relevant facts are front-loaded.

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?

For a five-parameter mutation tool with full annotation coverage, an 80%-documented schema, and no output schema, the description supplies everything an agent needs before calling: scope, merge behavior, conditional required fields, plan gating, and the fallback tool. Nothing material is missing.

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 coverage is 80%, so the baseline is 3, but the description earns above that by stating a rule the schema cannot express: stamps_required and reward_text are conditionally mandatory on the first call even though only business_id appears in the schema's required list. It also characterizes each field's meaning (how many stamps earn a reward, whether the card is live) in business terms.

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?

The description opens with a specific verb and resource ("Set up or change the business's loyalty stamp card") and then enumerates the configurable surface: stamp count, reward text, live status, and appearance. No sibling tool in the catalog touches loyalty cards, so the resource itself is distinguishing, and an agent can tell exactly what this call affects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states the partial-update contract ("Only provided fields change"), a creation-time prerequisite ("the first call must include stamps_required and reward_text"), and a plan prerequisite with the concrete failure mode and remediation ("402 plan_required otherwise — offer create_checkout_link"). That is explicit when-to-use and when-you-cannot-use guidance plus a named alternative path, not just implied usage.

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