Skip to main content
Glama

Lokand Restaurant MCP

Remove block

remove_block
Destructive

Remove a block (and any blocks nested in it).

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>",
      "block_id": "<block_id>"
    },
    "name": "remove_block"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare this as a destructive, non-idempotent, open-world write operation. The description adds meaningful context beyond that by disclosing the cascading behavior ('and any blocks nested in it'), which is important for an agent to know before deleting. It does not mention permission requirements, reversibility, or what happens on repeated calls, leaving some behavioral gaps.

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?

The description is a single front-loaded sentence with zero wasted words. Its brevity is appropriate, though it could still include a short usage clause without becoming bloated.

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?

The combination of annotations, a 75%-documented schema, and the cascade disclosure makes this minimally adequate for a destructive mutation tool. However, it lacks usage guidance and any mention of prerequisites or failure modes that would help an agent call it safely and correctly.

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 description coverage is 75%, with three of four parameters documented in the schema (including where to obtain block_id and section_id). The description adds no parameter-level guidance, but the schema carries most of the burden, so a baseline 3 is appropriate.

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?

The description states a specific verb and resource ('Remove a block') and is clearly distinct from the sibling tools that remove pages or sections. It does not name the neighboring removal tools explicitly, so it stops short of perfect sibling differentiation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus remove_page or remove_section, no prerequisites such as obtaining IDs from get_site, and no mention of when removal should be avoided. The agent is left to infer everything about usage context.

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