Skip to main content
Glama

Lokand Restaurant MCP

Check compliance

check_compliance
Read-onlyIdempotent

Check a business's published menu against what a country's menu rules ask for — allergen and calorie declarations, price-list notices, banned surcharges, operator identity. Returns each requirement with its official sources, plus which ones the menu currently falls short of and the item ids involved. ADVISORY ONLY: it reports, it never changes the site, and it is not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
countryNoISO country to check against. Defaults to the business's own country_code; pass one explicitly to check against a market the business is considering.
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint=false, but the description goes further with an explicit 'ADVISORY ONLY: it reports, it never changes the site, and it is not legal advice' disclaimer — an important framing the annotations cannot express. It also discloses what is returned (each requirement, its official sources, the shortfalls, and the item ids involved), which matters because there is no output schema.

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 sentences, front-loaded with what is checked, followed by what is returned and the advisory caveat. Every clause carries information: rule categories, output shape, and the legal/read-only framing. No filler.

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 two-parameter read tool with no output schema, the description covers purpose, return contents, and safety framing well. Gaps remain around failure modes (no published menu, unsupported country) and which jurisdictions' rule sets are actually available, which an agent would need before committing to the call.

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?

With only 50% schema description coverage, the country parameter is well documented in the schema itself (ISO pattern, default to the business's own country_code, explicit override for prospective markets). The business_id parameter carries no description in either place; the description only implies it identifies the business whose published menu is audited. Adequate but not compensating for the undocumented parameter.

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?

Names a specific verb (check) and two concrete resources (a business's published menu, a country's menu rules), then enumerates the rule categories covered: allergens, calories, price-list notices, banned surcharges, operator identity. No sibling in the list performs compliance checking, so the tool is trivially distinguishable.

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?

Usage is implied by the phrasing 'a business's published menu' and by the country parameter's note about checking against a market the business is considering, which is a genuine use-case hint. However, the description never states prerequisites (the business must already have a published menu), when not to use it, or what happens if no menu exists — an agent must infer these.

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