Skip to main content
Glama

面灵AI 面试助手

get_login_devices

Read-only

查看近 7 天登录过该账号的设备数量,以及是否检测到两台以上电脑(网页或客户端)登录,用于判断账号是否被他人共用。(需要用户授权,范围 account:read)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description need not re-establish safety. It does add context the annotations cannot carry: the 7-day lookback window, the specific 2+ computer detection rule, and the authorization prerequisite with its account:read scope, which tells the agent a user consent step is required before calling.

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?

It is a single front-loaded sentence stating what is returned, followed by the purpose and then the permission requirement in parentheses. Every clause carries distinct information, with no restatement of the tool name or filler.

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?

With no output schema and no parameters, the description carries the burden of explaining what comes back, and it does: a count of devices and a flag for two-or-more computer logins. Only the exact response shape and any empty-state behavior are left unstated, which is a minor gap for a simple read.

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 tool takes zero parameters, so the baseline is 4. The description does not introduce parameters that do not exist, and the fixed 7-day window is a useful implicit constraint on how results should be interpreted.

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 names a specific verb and resource (查看…登录过该账号的设备数量) and precisely delimits the scope: the last 7 days, device count, and whether two or more computers (web or client) logged in. That level of specificity makes the tool readily distinguishable from the security-status siblings such as get_sms_relay_status or get_voiceprint_status without opening any 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 states the decision the tool supports (用于判断账号是否被他人共用), which tells an agent when this call is appropriate. It does not name an alternative tool or state exclusions, but no sibling appears to overlap, so the guidance is clear context rather than a full routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources