Skip to main content
Glama

line_read_messages

Read recent messages from one LINE chat, newest first, so you can review conversation context within your MCP client.

Instructions

(Beta) Reads the latest messages of one LINE chat, newest first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two useful traits: beta status and newest-first ordering. It says nothing about how the target chat is determined with zero parameters, how many messages are returned, pagination, or auth requirements.

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 short sentence with the beta flag and the resource up front and the ordering detail appended. Nothing is wasted and there is no filler.

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?

For a zero-parameter read tool with no output schema and no annotations, the definition covers purpose and ordering but not the critical question of which chat is read or how results are shaped. An agent can guess intent but cannot predict behavior fully.

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 zero parameters the baseline would be 4, but the description refers to "one LINE chat" as though a chat selector existed, while the schema exposes no properties at all. That mismatch creates ambiguity the schema cannot resolve, so it falls below the zero-param baseline.

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 ("Reads the latest messages") scoped to a named platform (LINE) and distinguishes itself implicitly from line_search_messages by saying "latest" rather than search. However, "of one LINE chat" is undercut by the tool taking zero parameters, leaving how the chat is identified unclear.

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 phrase "latest messages" implies a recency-based read versus a query-based search, which is enough to steer an agent away from line_search_messages for browsing recent history. There is no explicit when-to-use statement, no stated prerequisites (e.g. line_connect), and no exclusions.

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