Skip to main content
Glama
JMComic AI

JMComic AI

by hect0x7

login

Authenticate with JMComic to access favorites, daily check-in, and restricted manga. Provide username and password to enable session-based queries and downloads.

Instructions

登录 JMComic 账户以访问更多功能(如收藏夹、每日签到、受限本子等)。 登录后的会话状态仅保存在当前运行内存中(不落盘),供当前会话后续查询和下载请求共享。

参数: username: 用户名 password: 密码

返回: 登录成功或失败的消息。

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": {
      "username": "<username>",
      "password": "<password>"
    },
    "name": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
usernameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: the session lives only in process memory and is never persisted to disk, so it is shared by later requests but lost on restart. However, it does not state what happens on failed credentials, whether any state is changed server side, or the credential-handling expectations, which matter for an auth tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, putting the purpose first and then the session-lifetime note and parameters. The parameter and return sections partially duplicate the input and output schemas, which is minor padding but not a distraction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description need not explain return values, and it adds the one piece of runtime context an agent cannot get from structured fields: the session is in-memory only and shared across later calls in this session. For a two-parameter auth tool, that is sufficient to call it correctly.

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 schema description coverage is 0%, so the description is expected to compensate, and it only translates the parameter names (username: 用户名, password: 密码) rather than adding meaning, such as whether an email or account ID is accepted or any encoding requirement. The parameters are largely self-explanatory, which keeps this above a 2, but the description adds nothing to the structure itself.

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?

The description uses a clear verb+resource (登录 JMComic 账户) and immediately qualifies the benefit (收藏夹、签到、受限本子), which lets an agent distinguish this authentication tool from all the browsing/downloading siblings. It does not explicitly contrast with siblings such as daily_checkin, which may itself require a session, so it stops short of a 5.

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?

It gives useful context for when to use it: login unlocks features that are otherwise unavailable, and it states that the resulting session is shared by subsequent query and download requests in the current session. What it lacks is an explicit statement of when not to call it (for example, if a session already exists) or whether repeated logins are needed.

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