Skip to main content
Glama

Lokand Restaurant MCP

Set translations

set_translations

Write translations of a business's menu into one locale: section names, dish names and descriptions, menu names, and the business name/description. Use the menu's own wording when the owner has it (e.g. a bilingual printed menu) rather than machine-translating. Fields you leave out keep their current translation. Visitors see a locale once it is in the business's supported_locales (update_business).

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>",
      "locale": "<locale>"
    },
    "name": "set_translations"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
menusNo
localeYesTarget locale, e.g. en
businessNo
categoriesNo
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already cover the safety traits (readOnlyHint=false, destructiveHint=false, openWorldHint=true) and the title repeats the name, so the description's credit comes from the partial-update semantics: fields left out keep their current translation, and the visibility dependency on supported_locales. That is meaningful behavior an agent could not infer from annotations alone.

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, front-loaded with what is written and to whom, followed by source-quality guidance and the visibility caveat. No sentence is redundant and nothing repeats the schema or title.

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 six-parameter tool with nested objects, no output schema, and low schema description coverage, the description covers every payload group and the key behavioral caveats. Minor gaps remain around business_id, the maxItems limits, and whether referenced item/category IDs must already exist.

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 only 17%, so the description carries the burden, and it largely does so: it enumerates the intent of the nested arrays (categories as section names, items as dish names/descriptions, menus, business) and states the single-locale constraint on locale. It does not explain business_id or the per-array limits, so it falls slightly short of full coverage.

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 names a specific verb (write translations) and pins down the exact resource scope: section names, dish names and descriptions, menu names, and the business name/description for a single locale. It is clearly distinguishable from update_business, which is cited only for the separate visibility step.

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

Usage Guidelines4/5

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

The description gives real operational guidance — prefer the owner's own wording (e.g. a bilingual printed menu) over machine translation, and note that a locale is only visible to visitors once it is in supported_locales via update_business. It lacks an explicit statement of when not to use this tool versus siblings, but the routing to update_business for the gating step is a concrete alternative.

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