Skip to main content
Glama

Lokand Restaurant MCP

Update qr design

update_qr_design

Change how the business's printed QR codes look. Only the fields you pass change. The code color must be darker than the background with enough contrast to scan — rejected otherwise. reset: true restores the default look.

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

Input Schema

NameRequiredDescriptionDefault
bgNoBackground behind the code
fgNoCode color (dark modules)
ctaNoOptional text above the code, e.g. "Scan to order". null = none (only the name is printed)
logoNoPut the business logo in the middle
frameNonone (code + label only), caption (call-to-action text above the code) or card (filled color card around the code)
resetNo
accentNoFrame color: caption text, card fill
eye_styleNoCorner markers: square, rounded or circle
business_idYes
module_styleNosquare (classic), rounded (soft, joined) or dots

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, open-world write, so the bar is lower; the description still adds real behavior: patch semantics rather than overwrite, a hard validation rule (code color must be darker than background with sufficient contrast or the request is rejected), and that reset:true restores defaults. It does not describe the failure payload or whether the updated design is returned.

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 short sentences, front-loaded with the purpose, then the patch contract, then the validation rule, then the reset escape hatch. No filler and nothing repeated from the schema.

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?

For a 10-parameter styling mutation with annotations but no output schema, this covers the essentials: what mutates, partial-update semantics, the one rejection rule, and reset. Only the response behavior and the business_id scoping are left implicit, which is minor.

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 baseline is 3; the description earns an extra point by supplying cross-field meaning the schema cannot express (fg must be darker/contrast against bg) and by explaining the undocumented reset parameter ('restores the default look'). Enum parameters like frame and module_style remain explained only by 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 concrete verb and resource — 'Change how the business's printed QR codes look' — which clearly marks it as the mutating counterpart to the sibling get_qr_design. It stops short of naming that sibling to route the agent, so it is clear but not fully differentiated in text.

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?

'Only the fields you pass change' implies this is a partial-update operation rather than a full replace, which is genuine usage guidance. However, it never says when to use this versus get_qr_design or update_theme, and gives no prerequisite (e.g., that a design must already exist).

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