Skip to main content
Glama

My active sign-in sessions

security_sessions_list
Read-onlyIdempotent

Your active sign-in sessions on the Barmaan website, most recently used first: browser, operating system, device type, country, when it started, when it was last used and how it signed in. IP addresses are not shown here. Signing a device out is only possible on the website (Account, Security).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, idempotent and closed-world, so the bar is lower. The description still adds real behavioral context beyond them: result ordering, the exact fields surfaced, the deliberate exclusion of IP addresses, and the fact that no sign-out action is available here. It does not mention pagination or result caps, which is the main remaining gap.

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?

Three short sentences, front-loaded with the resource and ordering, then the returned fields, then the two constraints. The field enumeration is dense but each item earns its place as a preview of the untyped return shape. Minor cost: the middle sentence is a long comma-run that reads as a list dump.

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 input parameters, no output schema, and full annotation coverage of the safety profile, the description carries the remaining burden well by enumerating returned fields and stating what is excluded. An agent has everything needed to call it and interpret the result.

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 there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter hints are present.

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 resource and scope: 'Your active sign-in sessions on the Barmaan website,' plus ordering ('most recently used first'). It clearly signals this is a read-only enumeration of the caller's own sessions, and the note that signing out is only possible on the website implicitly distinguishes it from a revoke-style sibling. It stops short of explicitly routing against the closest sibling, security_activity_list.

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?

Usage is implied rather than stated: an agent can infer this is the tool for 'what devices am I signed in on right now,' and the final sentence usefully rules out remediation via this tool. However, there is no explicit when-to-use vs. security_activity_list (which presumably covers sign-in history rather than current sessions), so the agent must infer the boundary.

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