Skip to main content
Glama

line_connect

Link LINE to LMCP by scanning a QR code in the LINE app, letting AI clients access LINE through your local MCP server.

Instructions

(Beta) Link LINE to LMCP with a QR code scanned in the LINE app.

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": "line_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful behavioral trait: linking is interactive and requires a QR scan in the LINE app, not a parameterized call. However it omits what the call actually returns (QR image, URL, or a pending handle), whether it blocks waiting for the scan, and what happens to an existing LINE link. The '(Beta)' marker adds stability context.

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 the mechanism attached and no filler. Every element (beta status, target service, QR flow) earns its place.

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?

There is no output schema and no annotations, so the description is the only source of truth for a zero-parameter, interactive auth tool, yet it never explains how the QR code is delivered to the agent or caller. That is the one fact an agent most needs before invoking it.

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 takes zero parameters, so the schema leaves nothing to explain and the baseline applies. The description correctly implies no input is needed and that the QR step happens outside the tool call.

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?

States a specific verb and resource ('Link LINE to LMCP') plus the linking mechanism (QR code scanned in the LINE app). It is clearly distinguishable from the sibling line_disconnect without naming it, though it never explicitly frames the connect/disconnect pair.

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?

Usage is only implied: the agent can infer this is the setup step that precedes line_list_chats, line_read_messages, etc., but the description never says when to call it, whether an existing linkage must be disconnected first, or what to do if the account is already linked.

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