Skip to main content
Glama

auth_request_login

Registers or resets a source account identity as login_required and clears any lease; use it to queue accounts for login on the external login site, not to perform authentication.

Instructions

Register or reset an identity as login_required (the 需登录队列).

Only writes crawl_identities + a note identity_event — the login itself happens on the login site (headful, via the observation channel); this tool never executes it. An existing identity is reset (status -> login_required, lease cleared); a new one is registered with the given automation level (auto | assisted).

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": {
      "source": "<source>",
      "account_alias": "<account_alias>"
    },
    "name": "auth_request_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesthe source the identity belongs to.
automationNologin unit's declared level (default "assisted").assisted
account_aliasYesthe account alias in that source's pool.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the basic write profile is covered. The description adds real value by naming exactly what gets written (crawl_identities plus a note identity_event) and that resetting clears an existing lease, which is a state effect not visible from annotations. It stops short of stating permissions, failure modes, or whether the reset is reversible for a held lease.

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?

Three tight sentences with the state-change semantics front-loaded and the key constraint (this tool never performs the login) placed immediately after the purpose. The parenthetical Chinese queue name is the only decoration, and it disambiguates rather than pads.

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?

An output schema exists, so return values need not be described, and the mutation semantics plus the queue target are well covered for a three-parameter tool. The remaining gap is the handoff to the actual login execution path, which an agent would still have to discover from sibling names.

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 100%, so 3 is the baseline, but the description goes further by specifying the allowed automation levels (auto | assisted) and tying registration to that level, information the schema does not enumerate. It says nothing extra about source or account_alias beyond what the schema already documents, which is acceptable.

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 gives a specific verb pair and resource ("register or reset an identity as login_required") and defines the queue it lands in, so the state transition is unambiguous. It also implicitly separates itself from the login-execution sibling by stating the login "never executes it" here, letting an agent tell the two apart without opening either schema.

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 clearly frames the operation: use it to enqueue/reset an identity, and clarifies that the actual login happens elsewhere on the login site. What's missing is an explicit pointer to the sibling that performs the login, so the agent must infer the handoff from behavior rather than a named alternative.

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