Skip to main content
Glama
Sign In
@zients/line-mcp-server

@zients/line-mcp-server

by zients
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Cancel Default Rich Menu

cancel_default_rich_menu

Cancel the default rich menu to remove it from your LINE bot. Use this to stop displaying the default rich menu when it is no longer needed.

Instructions

Cancel the default rich menu.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cancel_default_rich_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior1/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Cancel the default rich menu' without explaining what cancellation entails—whether it removes the default assignment, deletes the menu, or affects users. No side effects, reversibility, or prerequisites are disclosed.

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, concise sentence that is front-loaded with the action. It is appropriately sized for a simple tool, though it lacks any supplementary context.

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?

The description is too terse to be complete. It does not explain the effect of canceling the default rich menu, such as whether it deletes the menu or just unsets it. Given the simplicity of the tool, a brief clarification of the action's scope would suffice.

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

Parameters4/5

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

The tool has zero parameters, so the description does not need to add parameter semantics. The baseline of 4 is appropriate since there is nothing to clarify or expand upon.

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?

The description clearly states the action 'Cancel' and the resource 'default rich menu'. It distinguishes from sibling tools like set_default_rich_menu and delete_rich_menu by specifying the default setting, making the intent unambiguous.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention that this is the inverse of set_default_rich_menu, nor does it clarify differences from delete_rich_menu. An agent is left to infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools