Authenticate with your JMComic account to unlock member features such as favorites and premium content. Your session is saved for subsequent requests.
登录 JMComic 账户以访问更多功能（如收藏夹、高级内容等）。 登录后的会话 Cookie 会自动保存，供后续请求使用。
参数: username: 用户名 password: 密码
返回: 登录成功或失败的消息。
| Name | Required | Description | Default |
|---|---|---|---|
| password | Yes | ||
| username | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosing side effects. It transparently states that a session cookie is saved for future requests. It does not discuss credential handling or possible failure modes, but the core side effect is disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, direct, and well-structured with clear sections for purpose, side effect, parameters, and return value. Every sentence adds useful information without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple login tool, the description covers the purpose, the session-cookie side effect, the parameters, and the expected return message. It is complete enough for an agent to understand when and how to invoke the tool successfully.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides only bare parameter names with no descriptions, and the description merely restates them as '用户名' and '密码' without adding any constraints, formats, or behavioral details. Since schema coverage is effectively zero, the description needed to compensate and did not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'login' and the resource 'JMComic account', and explains the purpose of accessing additional features. It is distinct from the sibling tools, which are all album/comment/option operations, leaving no ambiguity about what this tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains when to use the tool: to access more features like favorites and premium content. It also notes that the session cookie is automatically saved for future requests, implying login should occur before other authenticated operations. It does not explicitly mention alternatives, but no sibling tool performs authentication.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.