Skip to main content
Glama

Lokand Restaurant MCP

Get business

get_business
Read-onlyIdempotent

Look up a public Lokand restaurant/business by its slug. Returns profile, hours, contact info, locale and theme metadata.

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": {
      "slug": "<slug>"
    },
    "name": "get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe business's public slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the scope of the payload ('profile, hours, contact info, locale and theme metadata'), which is otherwise unavailable because there is no output schema, and by marking the lookup as 'public', implying no authentication-gated data. The only gap is failure behavior for an unknown slug.

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 short sentences, zero filler: the action and lookup key come first, then the return payload. Every clause carries information an agent would otherwise have to guess at.

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?

This is a simple one-parameter read with full annotation coverage, and the description compensates for the missing output schema by summarizing the returned fields. What remains unstated is error/not-found behavior and whether unpublished or non-public businesses are excluded, which is a modest gap rather than a blocking one.

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 100% for the single required 'slug' parameter, whose own schema text explains it is the business's public slug. The description's phrase 'by its slug' / 'public' only reinforces that framing rather than adding syntax, source, or format guidance. Baseline 3 applies when the schema already carries the parameter meaning.

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 gives a specific verb ('Look up'), a specific resource ('public Lokand restaurant/business'), and the lookup key ('by its slug'), so an agent can tell this apart from list_businesses or update_business without opening any schema. It does not explicitly name a sibling, which keeps it just short of a 5.

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 only implied: the agent can infer this is the single-record read path used when a slug is already known, and that it is a public-facing lookup. There is no explicit statement of when to prefer it over list_businesses, and no precondition such as 'slug must come from list_businesses or a site URL'.

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