Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Завершить вход на устройстве

sessions_revoke
Destructive

Terminate a panel session by ID from the session list to remove that device; access and integration tokens remain active. Use all to end logins on every device.

Instructions

Завершает сессию по идентификатору из sessions_list — устройство выкинет из панели. На токены доступа не влияет.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNotrue — завершить входы на всех устройствах. Токены интеграций продолжают действовать.
session_idNoИдентификатор сессии из sessions_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / all
      Added value: +{
+  "description": "true — завершить входы на всех устройствах. Токены интеграций продолжают действовать.",
+  "type": "boolean"
+}
    • addedInput schema / properties / session_id / format
      Added value: +"uuid"
    • addedInput schema / properties / session_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / required
      Removed value: -[
-  "session_id"
-]
  2. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful scope detail beyond them: the device is ejected from the panel, and access tokens are explicitly unaffected (with integration tokens likewise continuing per the schema). This clarifies exactly what is and is not destroyed, which is valuable for a destructive operation.

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 short sentences: the action is front-loaded, followed by the token-impact caveat. No filler or redundancy; every clause carries information.

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?

For a simple two-parameter destructive mutation with no output schema, the description covers purpose, effect, and token scope adequately. The main gap is that neither parameter is required, yet the description never notes that a caller must supply either session_id or all=true, leaving that inference to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both parameters (all, session_id) are fully documented in the schema, so the baseline is 3. The description repeats that session_id comes from sessions_list but adds no format, constraint, or mutual-exclusivity detail beyond what the schema already provides.

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 states a specific verb and resource ('Завершает сессию по идентификатору') and names the sibling sessions_list as the source of the ID, so the agent can tell it apart from the listing tool. It does not, however, contrast with other account/security siblings such as operbots_logout, so differentiation is partial rather than complete.

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 only implied: the description tells the agent the ID comes from sessions_list, which signals the intended workflow, but it offers no explicit when-to-use guidance, no exclusions, and does not mention the 'all' variant covered only by the schema.

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

Deploy Server

Other Tools