Skip to main content
Glama

Lokand Restaurant MCP

List assets

list_assets
Read-onlyIdempotent

List every image the business owns: its media library (uploads, photos copied from its old website at import, photos the owner attached in chat), its logo and every menu item photo. Each entry has its url, kind, source, where it is used, and tags a vision model read off the image: subject (dish, drink, interior, exterior, people, logo, menu), what it shows, whether it matches the dish it is labelled as, quality 1-5, dominant colors and alt text. Use these urls for any site or menu image; never use an outside image.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly photos or only logos; default any
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description goes further by disclosing provenance categories (uploads vs. import-copied vs. chat-attached) and the full per-entry payload including vision-model tags, match flag, quality 1-5, dominant colors and alt text. That is real behavioral context an agent cannot get from the annotations, and nothing contradicts them.

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?

Purpose and scope are front-loaded in the first clause, with the field inventory and then the usage constraint following in logical order. The middle field list is dense and long, but each item (match flag, quality, colors, alt text) conveys distinct information rather than padding.

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?

With no output schema, the description correctly spends its length describing the return payload, so an agent knows what fields to expect. Remaining gaps are secondary: no mention of ordering, pagination, or behavior when the business has no assets, which matters for a list tool on a possibly large library.

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 50% (kind is documented, business_id is not), so the description needs to carry weight, and it does by characterizing the asset kinds and their sources, which maps onto the photo/logo/any enum. It does not explicitly restate the filtering behavior of the kind parameter or clarify the required business_id, leaving a modest gap.

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?

Opens with a specific verb and resource ("List every image the business owns") and immediately enumerates the concrete scopes it covers: media library uploads, imported legacy-site photos, chat attachments, logo, and menu item photos. That is enough for an agent to distinguish it from siblings like list_menus or get_site without inspecting any schema.

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?

Ends with an explicit directive: "Use these urls for any site or menu image; never use an outside image," which tells the agent both when to reach for this tool and a hard constraint on what to do with the result. It stops short of naming an alternative or exclusion case (e.g. what to do if an image is missing), so it is strong but not complete when/when-not guidance.

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