@zients/line-mcp-server

Get Bot Info

get_bot_info

Retrieve LINE Official Account bot details including name, ID, chat mode, and mark-as-read mode.

Instructions

Get information about the LINE Official Account bot, including name, ID, chat mode, and mark-as-read mode.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 4, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It indicates a read operation ('Get information') and lists the returned fields, but it does not mention side effects (likely none), authentication requirements, rate limits, or error behavior. For a zero-parameter getter, this is acceptable but not richly detailed.

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?

The description is a single, concise sentence that front-loads the action and resource, then specifies the key returned fields. Every word earns its place, with no filler or redundant phrasing.

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 tool with no parameters, no output schema, and no annotations, the description covers the essential purpose and the type of information returned. It does not specify the output format or any conditions, but given the simplicity of the operation, the definition is adequate for an agent to invoke it correctly.

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 input schema is an empty object with 0 parameters, so schema coverage is 100% by default. The description correctly omits parameter details because there are none. It adds value by enumerating the fields returned, which is helpful for agents expecting a structured response.

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 verb 'Get' and the resource 'information about the LINE Official Account bot', and lists specific fields (name, ID, chat mode, mark-as-read mode). This is distinct from all sibling getters which target users, groups, rooms, rich menus, or analytics, so there is no confusion with alternatives.

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

Usage Guidelines4/5

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

While no explicit when-to-use or exclusions are stated, the purpose is self-evident and there is no overlapping sibling for bot info. The description implicitly signals that this is a read-only retrieval tool to be used when bot-level settings are needed, though it could mention that it does not require parameters or prerequisites.

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

Deploy Server