Skip to main content
Glama

Lokand Restaurant MCP

Set nav links

set_nav_links
Destructive

Replace the navigation with custom links ([] restores the automatic page list).

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

Input Schema

NameRequiredDescriptionDefault
linksYesCustom navigation; [] restores the automatic page list
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; 'Replace' in the description is consistent with that and clarifies that existing nav links are discarded wholesale rather than merged. It adds the reset semantics, but says nothing about authorization requirements, whether the change is immediate/live, or why idempotentHint is false for an operation that otherwise looks repeatable.

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 front-loaded sentence with the replace behavior stated first and the empty-array escape hatch in parentheses. No filler; the only minor cost is that the parenthetical duplicates the schema's links description.

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 tool is simple (two required params, nested array constraints fully specified in the schema, no output schema), and the description covers the core mutation and reset case. It stops short of stating prerequisites or the effect on live navigation, which for a destructiveHint=true setter would meaningfully help an agent avoid misuse.

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?

With only 50% schema description coverage, the undocumented business_id gets no explanation in the description. The links semantics it does explain ('[] restores the automatic page list') merely restates the schema's own description for that property, so little meaning is added beyond structured fields.

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 gives a specific verb ('Replace') and resource ('the navigation') plus the payload type ('custom links'), so an agent knows exactly what state change is performed. It does not differentiate itself from sibling setters (e.g. set_brand_link, set_theme), but the purpose itself 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 Guidelines3/5

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

The parenthetical '([] restores the automatic page list)' is genuine usage guidance for the reset case, so the agent knows how to undo a customization. However, there is no statement of when to prefer this over siblings, what preconditions exist (site claimed, theme applied), or whether partial updates are possible.

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