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

@zients/line-mcp-server

by zients
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Default Rich Menu

get_default_rich_menu

Fetch the default rich menu's ID to identify which rich menu is currently set as the default for the LINE account.

Instructions

Get the ID of 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": "get_default_rich_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. 'Get' clearly implies a read-only retrieval and the result is named as the ID, but the description doesn't disclose what happens when no default rich menu is set or describe the return shape. This is a small but real gap.

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?

A single, front-loaded sentence with no filler. Every word contributes directly to the tool's purpose.

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 zero-parameter getter, this is nearly complete: the agent knows what to call and what result to expect. However, the absence of an output schema and the unstated no-default behavior keep it from being fully self-sufficient.

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 and the schema description coverage is 100%, so there are no parameter semantics to document. The baseline of 4 applies because nothing more is needed.

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 uses a specific verb and resource: 'Get the ID of the default rich menu.' It clearly distinguishes this from sibling tools like set_default_rich_menu, cancel_default_rich_menu, and get_rich_menu by focusing on reading the current default.

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 intended use is implied: call this when you need the default rich menu ID. However, it doesn't explicitly say when to prefer this over list_rich_menus, get_rich_menu, or set_default_rich_menu, so the guidance is left to inference rather than stated.

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