Skip to main content
Glama

Lokand Restaurant MCP

Get qr design

get_qr_design
Read-onlyIdempotent

Read how the business's printed QR codes look: colors, module and corner style, frame, call-to-action and whether the logo is in the middle.

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

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety behavior is covered and the description does not need to repeat it. What the description does add is genuinely useful: with no output schema, it is the only source describing what the response contains (colors, module/corner style, frame, CTA, logo presence). It still omits behavior such as what happens when no design is configured or whether defaults are returned.

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 front-loaded sentence with no filler: the verb and resource come first and the returned facets follow as a list. It is efficiently scoped, though the long inline enumeration is slightly harder to scan than a short lead sentence plus a compact list.

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 single-parameter read tool with rich annotations, the description covers what comes back, which is its main job given there is no output schema. It falls short on the one required parameter, on the empty-state behavior, and on directing the agent to update_qr_design for mutations, leaving the definition adequate but with 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 parameter, business_id, with 0% schema description coverage, so the description would need to carry the burden of explaining it and does not mention it at all. The only required input is left completely undocumented beyond its self-evident name, and there is no hint about identifier format or where the business_id comes from.

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 leads with a specific verb and resource, 'Read how the business's printed QR codes look,' and then enumerates the design facets covered: colors, module and corner style, frame, call-to-action, and logo placement. That makes the scope of retrieved data unambiguous and implicitly separates it from the update_qr_design sibling, though it never names that alternative.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no mention of a prerequisite (such as the business needing an existing QR design), and no pointer to update_qr_design for changes or export_qr_codes for output. The read-oriented verbs imply a retrieval context, but that is left for the agent to infer.

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