Skip to main content
Glama

Lokand Restaurant MCP

Use asset

use_asset

Put one of the business's own images (a url from list_assets) to use: as the logo (target "logo") or as a menu item's photo (target "item" with item_id). For a site section or block image, pass the same url to update_section / update_block instead.

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>",
      "url": "<url>",
      "target": "<target>"
    },
    "name": "use_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAn image url from list_assets
targetYes
item_idNoThe menu item, for target item
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description does not need to re-state that this is a mutation. It adds the sourcing constraint that the url must come from list_assets, but says nothing about what happens to a previously set logo/photo, whether the image must be pre-uploaded, or permission requirements — a meaningful gap for a write tool whose idempotentHint is false.

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, zero filler: the primary action and its two targets come first, followed by the routing rule to sibling tools. Every clause carries information an agent needs to pick correctly.

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 4-parameter write tool with no output schema, the description covers the action, the valid targets, the required helper parameter, and the alternative tools. The remaining gap — replacement semantics for an already-set logo/photo — is real but modest against annotations that already disclose the non-destructive, non-idempotent profile.

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%, and the description compensates well on the weak spot: the target enum has no schema description, yet the text explains its two values and the conditional coupling between target="item" and item_id. Only business_id is left entirely to the schema, which is a minor omission given it is a standard tenant identifier.

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?

Uses a specific verb phrase ("put ... to use") with a specific resource (one of the business's own images), and immediately names the two supported targets ("logo", "item"). It also distinguishes itself from update_section/update_block, so an agent can tell which tool handles which image slot without opening another schema.

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

Usage Guidelines5/5

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

Explicitly states the selection rule: use this tool for logo and menu-item photos, and use update_section/update_block for section or block images. Both the when-to-use and the alternative-if-not case are stated, leaving nothing to inference.

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