Skip to main content
Glama

Lokand Restaurant MCP

Publish site

publish_site
Destructive

Publish (or unpublish) the business's public menu site at https://.lokand.co.

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

Input Schema

NameRequiredDescriptionDefault
publishNotrue to go live, false to take the site offline
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is known from structured data rather than the description. The description adds the publicly visible URL, but says nothing about propagation delay, caching, whether the site must be configured first, or that unpublishing takes a live site offline for end users — meaningful gaps for a destructive, non-idempotent operation that no annotation can cover.

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?

A single well-formed sentence that front-loads the action and ends with the concrete URL pattern; nothing is wasted, though the brevity is also the source of the missing guidance.

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

Completeness2/5

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

For a destructive publish/unpublish toggle with no output schema and an undocumented required business_id, the agent still lacks how the slug is resolved, what the call returns (e.g., the live URL), and confirmation or precondition guidance. The description covers the what but not enough of the how.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the 'publish' boolean is documented in the schema ('true to go live, false to take the site offline') while business_id is undocumented anywhere. The description's '(or unpublish)' only loosely mirrors the schema's publish semantics and adds nothing for business_id, so it does not compensate 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?

The description states a specific verb+resource ('Publish (or unpublish) the business's public menu site') and even names the resulting public URL pattern, so the agent knows exactly what is being toggled. It does not, however, distinguish this from sibling publishing tools such as publish_brand_template, theme_publish, or apply_site_preset.

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 versus the other publish-related siblings, no stated prerequisites (site must exist, theme applied, etc.), and no note about confirming before taking a live site offline. The only implied usage is the parenthetical '(or unpublish)', which hints the tool covers both directions.

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