Skip to main content
Glama
Sign In
line-oa-mcp-ultimate

line-oa-mcp-ultimate

by wasintoh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Switch active LINE OA

line_use_oa
Idempotent

Set the default LINE Official Account (OA) for all later tool calls by providing an OA ID from line_list_oas. Changes only apply in memory for this process.

Instructions

Switch which OA all subsequent tool calls default to (until changed or process restart). In-memory only — does not edit config.json. oa_id from line_list_oas.

Returns { active_oa, display_name }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "oa_id": "<oa_id>"
    },
    "name": "line_use_oa"
  }
}

Input Schema

NameRequiredDescriptionDefault
oa_idYesOA id from line_list_oas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations include idempotentHint=true and no destructive hint. Description adds that the change is only in-memory and persistent only for the session, which is valuable beyond annotations. It also specifies the return value.

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?

Extremely concise: two sentences clearly stating purpose and behavior, plus a return description. No unnecessary words. Front-loaded with the main action.

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 simple state-switching tool with one parameter, the description covers the action, side effects, parameter source, and return value. It is complete for the complexity level, though could note error handling briefly.

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?

The only parameter oa_id has 100% schema coverage with a description stating it comes from line_list_oas. The tool description repeats this but adds no extra meaning. Baseline 3 is appropriate.

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 tool switches the active LINE OA for subsequent calls, using the verb 'switch' and specifying the resource 'active OA'. It distinguishes from siblings like line_list_oas which lists OAs.

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?

The description explains when to use: to set the default OA for all following tools. It provides important context like in-memory only and the source for oa_id (from line_list_oas). Does not explicitly exclude scenarios but is clear enough.

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