Skip to main content
Glama

Lokand Restaurant MCP

Set page

set_page
Destructive

Change one page: enable/disable it, show/hide it in the navigation, rename its title, change its path, make it the home page, or move it in the navigation. Only provided fields change. Page ids come from get_site.document.pages (built-ins: home, menu, about, loyalty).

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>",
      "page_id": "<page_id>"
    },
    "name": "set_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOne segment like /wine
titleNo
enabledNo
page_idYesPage id, e.g. home, menu, about, loyalty
positionNoMove the page to this position in the navigation
make_homeNoServe this page at /
business_idYes
show_in_navNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, so the risk profile is declared. The description adds genuine value beyond that with partial-update semantics and the id provenance chain, though it never warns that changing path or making a page home can break existing links — a relevant caveat given the destructive flag.

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?

Three sentences, front-loaded with the action list, then the partial-update rule, then the id source. No filler and no repetition of the input schema's wording.

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 an 8-parameter mutation tool with no output schema, this covers what to change, how partial updates behave, and where ids come from. The remaining gap is the consequence of destructive operations (e.g., path changes orphaning old URLs), which the description never touches.

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 only 50%, yet the description maps nearly every optional parameter to a concrete action (enabled, show_in_nav, title, path, make_home, position), which is meaning the schema names alone don't convey. Only business_id is left unexplained, and its role is inferable from the context.

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?

States a specific verb ("Change one page") followed by a precise enumeration of the mutations supported (enable/disable, show/hide in nav, rename, path, make home, move). The verb+resource framing clearly separates it from add_page and remove_page, which do different things to pages.

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?

"Only provided fields change" establishes partial-update semantics, and the pointer to get_site.document.pages tells the agent where valid ids come from, including the built-in set. It does not explicitly say when to choose this over add_page/remove_page, but the mutation list makes the boundary self-evident.

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