Skip to main content
Glama

Lokand Restaurant MCP

Apply country settings

apply_country_settings
Destructive

Fill the business's menu display options with the values a country's rules suggest — a notice about tax-inclusive pricing, the price-effective date, ordering restrictions. These are DEFAULTS: the owner can change any of them afterwards, and nothing here is enforced.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for any suggested copy. Defaults to the business's.
countryNoDefaults to the business's own country_code.
overwriteNofalse (default) fills only options the owner hasn't set; true replaces their existing values.
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Adds useful context beyond annotations: suggested values are only defaults and can be edited later, and nothing is enforced. However annotations declare destructiveHint=true and non-idempotent behavior, while the description does not explain that overwrite=true replaces existing values or warn about the destructive path; emphasizing defaults can understate that risk.

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?

Two tightly written sentences; the key scope and the important 'these are defaults' caveat are front-loaded with no 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?

For a four-parameter mutation tool with no output schema, it explains intent and the default/non-enforcement model. However, it leaves the destructive overwrite behavior and the meaning of business_id to the schema and annotations, so it is adequate but not fully complete.

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

Parameters3/5

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

Schema covers 3 of 4 parameters at 75% coverage, including locale, country, and overwrite. The description adds examples of what settings get filled, but it does not add meaning to business_id or further clarify when overwrite should be used beyond 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?

Names a concrete action (fill menu display options) and concrete resource (country-suggested settings such as tax-inclusive notice, price-effective date, ordering restrictions). It is distinguishable from theme/preset siblings by its country-rules scope, though it does not explicitly name an alternative.

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?

Describes the intended setup context and stresses that values are defaults, but does not state when to choose it over related tools such as update_theme_settings or apply_site_preset, nor does it give preconditions or exclusions.

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