Skip to main content
Glama

line_disconnect

Unlinks LINE from LMCP by deleting the saved session on this Mac, helping you disconnect the account and clear local access.

Instructions

(Beta) Unlink LINE from LMCP: removes the session saved on this Mac.

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_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description alone carries the burden, and it does disclose the key trait: the effect is limited to the locally stored session, not remote account data. Beyond that, it says nothing about reversibility (re-link via line_connect), behavior when not currently connected, or whether cached chats survive.

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 beta marker and the destructive scope stated up front; no wasted words and nothing an agent must read past to find the effect.

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 teardown action with no annotations and no output schema, the description covers what the tool does and the scope of the change. It stops short of stating failure modes or reversibility, which is the only remaining gap.

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 there is no parameter meaning to explain and the schema leaves no gap to compensate for. Baseline of 4 applies.

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?

Uses a specific verb plus resource ("Unlink LINE from LMCP") and adds scope that a bare name would not convey: it removes "the session saved on this Mac." This clearly separates it from line_connect and from server-side revocation tools.

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 by the verb "Unlink" — the agent can infer it is the teardown counterpart of line_connect, but there is no explicit when-to-use, no prerequisite (e.g., must be connected first), and no stated alternative or when-not guidance.

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