Skip to main content
Glama

AceRound AI Interview Copilot

get_login_devices

Read-only

Show how many devices signed in to this account in the last 7 days and whether more than one computer (web or desktop app) was used, to tell whether the account is being shared. (Requires the user's sign-in with scope 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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint:false and openWorldHint:false, and the description adds the meaningful extra context the rubric calls for: the 7-day lookback window, the unit measured (devices and multi-computer use), and the required auth scope 'account:read'. It does not say whether results are cached or how the device count is derived, but for a zero-parameter read it is informative.

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?

One front-loaded sentence states what is returned and why, followed by a short parenthetical for the auth prerequisite. No filler, and the purpose appears before the caveat.

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?

With no output schema, the description itself explains what comes back: a device count over a fixed window plus a boolean-style signal about multiple computers. Combined with the disclosed auth scope and the existing read-only annotations, an agent has everything needed to decide and call correctly.

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 no parameters, so per the rubric the baseline is 4. The description correctly adds no parameter detail, and there is nothing for it to compensate for given 100% schema coverage.

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 names a specific verb and resource ('Show how many devices signed in to this account'), scopes it to the last 7 days, and states the returned indicator (more than one computer on web or desktop). It never names or contrasts a sibling tool, but the purpose is unmistakable against the listed siblings, which cover unrelated resources.

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 a clear use context ('to tell whether the account is being shared') and the prerequisite ('Requires the user's sign-in with scope account:read'). It stops short of explicit when-not-to-use guidance or naming alternatives, so it sits at 4 rather than 5.

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