Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Подключиться к панели

operbots_login

Authenticates to the operbots panel using a token from a local token_file; call when tools report access is not configured or the token has expired.

Instructions

Проверяет доступ или подключается по токену из локального token_file. Токен выпускается в самой панели: аккаунт → Интеграции → «Выпустить токен», и показывается там один раз. Человек вводит его через CLI login или локальный файл; формы MCP не запрашивают секреты. Вызывайте, когда другие инструменты сообщают, что доступ не настроен или токен больше не действует.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoАдрес панели. По умолчанию сохранённый адрес или http://localhost:8080.
token_fileNoАбсолютный путь к UTF-8 файлу с токеном. Значение читает локальный сервер, в переписку оно не попадает.
switch_accountNoПодключиться заново, даже если доступ уже настроен.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / token_file
      Added value: +{
+  "description": "Абсолютный путь к UTF-8 файлу с токеном. Значение читает локальный сервер, в переписку оно не попадает.",
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"Адрес панели, если он известен. Иначе его спросят в окне."New value: +"Адрес панели. По умолчанию сохранённый адрес или http://localhost:8080."
  2. Changed2 schema fields changedv0.1.13
    • changedInput schema / properties / switch_account / description
      Previous value: -"Войти под другой учётной записью, даже если вход уже выполнен."New value: +"Подключиться заново, даже если доступ уже настроен."
    • changedInput schema / properties / url / description
      Previous value: -"Адрес панели, если он известен. Иначе его спросят в окне входа."New value: +"Адрес панели, если он известен. Иначе его спросят в окне."
  3. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the real behavioral model: it validates or establishes an authenticated session, secrets are never entered through MCP forms, and token provisioning is manual and one-time. It does not discuss what happens to an existing session or token on reconnect, so it falls short of a 5.

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 sentences: the action first, then the token-sourcing and secrecy context, then the call trigger last. It is appropriately sized with no filler, though the token issuance detail is somewhat dense within a single sentence.

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, the description adequately covers what the tool does, when to call it, and the human-in-the-loop auth model for a 3-parameter tool. It does not state what a successful or failed connection returns, which is a minor remaining gap.

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%, so url, token_file, and switch_account are already documented in the schema with defaults and formatting notes. The description adds the conceptual context of where the token comes from but no parameter-level syntax beyond the schema, so the baseline 3 applies.

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: it checks access or connects to the panel using a token from a local token_file. It is clearly distinct from operbots_logout, which is its opposite, and from whoami. It does not explicitly name sibling tools, keeping it just below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit, actionable trigger: call it when other tools report that access is not configured or the token is no longer valid. It also explains where the token originates (account → Integrations → issue token) and the two ways a human supplies it, leaving nothing to inference.

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