Skip to main content
Glama

Lokand Restaurant MCP

Remove section

remove_section
Destructive

Remove a section from a page. To keep it for later, hide it with update_section hidden=true 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>",
      "page_id": "<page_id>",
      "section_id": "<section_id>"
    },
    "name": "remove_section"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the irreversibility signal is supplied structurally. The description adds the useful contrast between deletion and hiding, but says nothing about permissions, cascade effects on contained blocks, or whether removal is recoverable. With annotations carrying the safety profile, this is adequate but not rich.

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, action first and the safer alternative second. Zero waste and properly front-loaded.

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 3-required-param destructive delete with no output schema, the definition covers what is being deleted and the recommended alternative, which is the core decision information. It stops short of explaining effects on nested blocks or the source of business_id, leaving a small gap relative to a destructive operation.

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%, with page_id and section_id documented in-schema (including 'Section id from get_site'), while business_id is undocumented there. The description adds no parameter meaning at all, not even clarifying that section_id must come from get_site. Baseline 3 applies given moderate coverage, but it misses a chance to compensate for the business_id 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?

Specific verb + resource ('Remove a section from a page') that distinguishes it from siblings like remove_block, remove_page, and update_section. The object being acted on and its containment are unambiguous.

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 names the alternative path ('hide it with update_section hidden=true instead') and the condition that selects it (keeping the section for later). This is a clear when-not-to-use rule pointing at a named sibling.

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