Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

get_message_quota

Check monthly message quota and current usage for LINE Official Accounts to monitor API limits and manage messaging capacity.

Instructions

Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The register method defines and registers the "get_message_quota" tool with the MCP server, including its handler logic that calls the MessagingApiClient to fetch quota and consumption data.
    register(server: McpServer) {
      server.tool(
        "get_message_quota",
        "Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage.",
        {},
        async () => {
          const messageQuotaResponse = await this.client.getMessageQuota();
          const messageQuotaConsumptionResponse =
            await this.client.getMessageQuotaConsumption();
          const response = {
            limited: messageQuotaResponse.value,
            totalUsage: messageQuotaConsumptionResponse.totalUsage,
          };
          return createSuccessResponse(response);
        },
      );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the tool's behavior as a read-only operation that retrieves quota data, which is helpful. However, it lacks details on authentication requirements, rate limits, error conditions, or whether the data is real-time or cached. The description adds basic context but misses deeper behavioral traits.

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 two sentences with zero waste: the first states the action and resource, and the second clarifies the scope. It's front-loaded with the core purpose and efficiently structured, making every sentence earn its place without redundancy.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and the type of data returned (quota and usage). However, without an output schema, it could benefit from more detail on the response format (e.g., numeric values, units). The description covers the essentials but has a minor gap in output clarity.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. This aligns with the baseline expectation for zero-parameter tools, earning a high score for not adding unnecessary details.

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 specific action ('Get'), resource ('message quota and consumption of the LINE Official Account'), and scope ('monthly message limit and current usage'). It distinguishes itself from sibling tools like broadcast/push messages or rich menu operations by focusing on quota monitoring rather than message sending or UI management.

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 description implies usage context through 'monthly message limit and current usage,' suggesting this tool is for monitoring quota status. However, it doesn't explicitly state when to use it versus alternatives (e.g., before sending messages to check limits) or provide exclusions. The implicit guidance is adequate but not explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/acquo/line-bot-mcp-server-sse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server