Skip to main content
Glama

Lokand Restaurant MCP

Set featured items

set_featured_items
Destructive

Choose the dishes shown in the home page's "featured" section, in order (menu item ids, max 12; [] lets the site pick automatically). Adds the section after the hero if the page has none.

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>",
      "item_ids": "<item_ids>"
    },
    "name": "set_featured_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idNoDefaults to the home page
item_idsYesMenu item ids, in display order; [] = automatic
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description does add real context beyond that: it discloses the side effect of creating the section after the hero when none exists, and that an empty array triggers automatic selection (consistent with non-idempotency). It does not say what happens to previously featured items — whether they are replaced, unset, or merely re-ordered — which is the key missing disclosure for a destructive setter.

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?

Two tight sentences, front-loaded with the core action and the ordering constraint, then the edge-case behavior. The parenthetical packing is dense but every clause carries information; not a word is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with no output schema, the definition covers ordering semantics, auto-selection, and page defaulting, but leaves the overwrite behavior and business_id semantics unexplained. An agent could call it but might not predict what happens to existing featured items.

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 67%, and the description largely restates schema content: item ids in display order, max 12, [] = automatic, page defaults to home. The one uncovered parameter, business_id, gets no explanation in either place, and the description adds no format or constraint detail beyond the schema.

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?

States a specific verb and resource — choosing dishes for the home page's "featured" section — plus the ordering semantics of the input. An agent can tell this sets a curated list rather than editing a single item (add_item) or reordering an existing section (reorder_items), though it never names those neighbors explicitly.

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 resource it targets, and the note that [] hands selection back to the site is a useful conditional. However there is no explicit when-to-use vs. when-not-to-use guidance and no mention of alternatives such as reorder_items for changing order of an existing list.

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