Skip to main content
Glama

login_status

Checks login and health status, verifying credentials with the platform by default or only locally when verify=false.

Instructions

检查登录与健康,默认向平台验证。verify=false 仅检查本地凭据。

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": "login_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
verifyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavior, and it does disclose the meaningful trait that the default path contacts the platform while verify=false stays local — useful for latency and network considerations. It does not say what is returned, whether the call is read-only, or what 'health' checks mean.

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?

Two compact sentences: the core purpose first, then the default behavior, then the exception. No filler. Slightly terse for a description that has to carry all behavioral context alone.

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

Completeness3/5

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

For a one-optional-parameter, no-output-schema tool the essentials are present, but 'health' is left unexplained and there is no indication of what a positive or negative result looks like, which matters when the description is the only behavioral source.

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?

Schema coverage is 0% and the schema only declares a bare boolean. The description supplies the actual meaning — omitted/true means verify against the platform, false means check only local credentials — which is exactly the information the schema lacks.

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?

States a specific action (check login and health) and clarifies the two modes of the check. 'Health' remains undefined, and it doesn't explicitly distinguish itself from bili_qr_login or bili_qr_poll, but the verb and resource are clear enough to identify the tool.

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 default and the verify=false alternative are stated, which implies when a caller would want the lighter local check versus the platform round-trip. There is no explicit when-to-use versus siblings or when-not guidance beyond that default.

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