Skip to main content
Glama

Lokand Restaurant MCP

Update business

update_business
Destructive

Update a business's profile: name, description, about text, opening hours, contact info, currency, default locale, the locales visitors can switch between, menu display options, country, business details, or place (location, address, timezone, category, cuisines). Only provided fields change.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
aboutNo
hoursNoOpening hours keyed mon..sun, each {"open":"10:30","close":"22:00"} or {"closed":true}
placeNoWhere the business is and what kind of place it is: lat/lng; address {streetAddress, addressLocality (district), addressRegion (city or province), postalCode, addressCountry (ISO 3166-1 alpha-2)}; timezone (IANA, e.g. "Europe/Istanbul"); category (e.g. restaurant, cafe, bakery, bar, meyhane, fast_food, dessert_shop); up to 6 cuisines (e.g. turkish, kebab, seafood, sushi, vegan). Merged into what is stored: keys you pass replace, keys you leave out stay.
maps_urlNoA Google Maps, Apple Maps, Yandex or OpenStreetMap link (short share links work), or a "lat, lng" pair. Sets the coordinates.
legal_infoNoBusiness details published on the site when filled in: tradeName, taxNumber, registrationNumber, registeredAddress, contactEmail, contactPhone, plus `extra` label/value pairs for anything a jurisdiction names differently (a Vergi Dairesi, a US EIN). All optional.
business_idYes
descriptionNo
contact_infoNoContact info: phone, email, address, instagram
country_codeNoISO 3166-1 alpha-2 country the business operates in. ADVISORY: it seeds suggested menu options (apply_country_settings) and drives check_compliance. It never changes what the site renders.
menu_optionsNoHow the published menu presents itself: `menuNotice` (free text shown above the menu, in the owner's own words), `showPriceEffectiveDate`, and `orderingExcludedTags` (tags that can be listed but not ordered online, e.g. alcohol). This is the ONLY thing that changes what the site renders.
currency_codeNo
default_localeNo
supported_localesNoLocales visitors can switch between, e.g. ["pl","en"]; the default locale is always included

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / default_locale / enum
      Added value: +[
      +  "en",
      +  "tr",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "nl",
      +  "pl",
      +  "ja",
      +  "zh",
      +  "ar"
      +]
    • removedInput schema / properties / default_locale / maxLength
      Removed value: -10
    • removedInput schema / properties / default_locale / minLength
      Removed value: -2
    • addedInput schema / properties / supported_locales
      Added value: +{
      +  "description": "Locales visitors can switch between, e.g. [\"pl\",\"en\"]; the default locale is always included",
      +  "items": {
      +    "$ref": "#/properties/default_locale"
      +  },
      +  "maxItems": 12,
      +  "minItems": 1,
      +  "type": "array"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the agent knows this mutates state. The description adds one genuinely useful behavioral fact — "Only provided fields change" (patch semantics) — but it never addresses the destructive annotation (which nested writes replace rather than merge) or the null-vs-omit distinction implied by the nullable description/about fields. Auth and permission requirements are unmentioned.

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 the verb and resource leading, so the reader gets the operation immediately. The long field enumeration partly duplicates schema property names, but the closing clause "Only provided fields change" earns its place.

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 14-parameter mutation tool with nested objects and no output schema, the description is adequate on scope but thin on behavior. It omits the null-clearing semantics, which nested objects merge versus replace, and any destructive/irreversibility warning that the destructiveHint annotation implies the agent should be warned about.

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 coverage is 57%, and the richer parameters (hours, place, legal_info, menu_options, supported_locales, country_code, maps_url) already carry detailed schema descriptions. The prose list of editable fields maps names to groups but adds little semantic meaning beyond the schema, and it does not explain that passing null clears a field while omitting it leaves it unchanged — the single most consequential ambiguity across 14 parameters.

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?

"Update a business's profile" pairs a specific verb with the resource, and the enumeration of editable groups (name, about, hours, contact info, locales, menu options, place, legal details) makes scope concrete. It stops short of distinguishing itself explicitly from sibling mutators such as update_menu or update_site, so an agent must infer the boundary from the field list.

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 statement of when to use this tool versus alternatives — nothing about reading current values first via get_business, or why a field belongs here rather than in update_menu or update_site. Usage is only implied by the field enumeration, and no prerequisites (permissions, required business ownership) are stated.

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