Skip to main content
Glama

Lokand Restaurant MCP

Remove page

remove_page
Destructive

Remove a custom page and its sections. The home page can't be removed — make another page home first (set_page make_home).

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

Input Schema

NameRequiredDescriptionDefault
page_idYesPage id, e.g. home, menu, about, loyalty
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds real value beyond that: deletion cascades to the page's sections, and a hard precondition on the home page. It stops short of stating irreversibility or what identifying data is returned.

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, the destructive scope is front-loaded, and the constraint follows immediately. No filler or restatement of the tool name.

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 destructive two-parameter tool with no output schema, the description covers the crucial facts: what is destroyed alongside the page and the one precondition that blocks the call. Missing only a note on irreversibility/confirmation and the undocumented business_id.

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 50%: page_id has an example list, business_id has none. The description only implicitly clarifies page_id by mentioning 'the home page', and says nothing about business_id or what happens with a custom-vs-default page id. Adequate but not compensating for the coverage gap.

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 ('Remove a custom page') and scopes it with 'and its sections', which distinguishes it from remove_section and remove_block. It does not explicitly name those siblings, but the object of deletion is unambiguous.

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?

Gives a clear when-not condition (the home page cannot be removed) plus the concrete remedy ('make another page home first (set_page make_home)'), which even names the alternative tool. Lacks guidance on choosing this over remove_section/remove_block, but the constraint that matters most is covered.

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