Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Подключить или настроить ИИ-сервис

ai_save

Create or update AI service connections in the operbots panel, setting provider credentials, model, temperature, and history options.

Instructions

Без параметра provider подключает новый сервис, с ним — меняет настройки. Какие ключи нужны: gigachat — authorization_key (обязательно), scope (по умолчанию GIGACHAT_API_PERS); yandexgpt — api_key (обязательно), folder_id (обязательно); openai — api_key (обязательно); openrouter — api_key (обязательно); custom — api_key (по желанию); обязателен base_url. При изменении переданные ключи дописываются поверх прежних, а стереть ключ пустой строкой нельзя — только перезаписать.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
kindNoВид сервиса. Обязателен при создании, сменить его потом нельзя.
nameNoНазвание подключения в панели.
modelNoМодель. Известные: gigachat — GigaChat, GigaChat-Pro, GigaChat-Max, GigaChat-2 (по умолчанию GigaChat); yandexgpt — yandexgpt-lite, yandexgpt, yandexgpt-32k (по умолчанию yandexgpt-lite); openai — gpt-4o, gpt-4o-mini, gpt-4.1, gpt-4.1-mini, o4-mini (по умолчанию gpt-4o-mini); openrouter — openai/gpt-4o-mini, anthropic/claude-3.5-sonnet, google/gemini-2.0-flash-001, meta-llama/llama-3.3-70b-instruct, deepseek/deepseek-chat; custom — зависит от вашего сервера; поле обязательно заполнить вручную
activeNoВключено ли подключение.
optionsNoНастройки памяти, экономии контекста и сервиса. Заменяет карту: memory, summary_every, cache_context и другие поля API.
base_urlNoАдрес сервера. Обязателен для вида custom.
providerNoКакое подключение менять. Не указывайте, чтобы создать новое.
max_tokensNoПредел длины ответа. По умолчанию 1024.
credentialsNoКлючи доступа. Состав зависит от вида сервиса — см. описание инструмента.
temperatureNoРазброс ответов: 0 — строго по делу, 2 — свободно. По умолчанию 0.7.
history_depthNoСколько прошлых реплик подмешивать в запрос. По умолчанию 10.
system_promptNoПостоянная подсказка модели: как себя вести и о чём говорить.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / base_url / anyOf
      Added value: +[
+  {
+    "maxLength": 400,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / base_url / maxLength
      Removed value: -400
    • removedInput schema / properties / base_url / type
      Removed value: -"string"
    • addedInput schema / properties / options
      Added value: +{
+  "additionalProperties": {},
+  "description": "Настройки памяти, экономии контекста и сервиса. Заменяет карту: memory, summary_every, cache_context и другие поля API.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover safety (destructive=false, idempotent=false) and the description adds genuinely non-obvious behavior: on update, passed keys are merged over existing ones and cannot be erased with an empty string, only overwritten. This merge/no-erase constraint is exactly the kind of context structured fields cannot carry.

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?

Front-loads the provider create/update distinction, then a compact per-provider key list, then the merge caveat. Dense but every clause earns its place; the enumeration is long but necessary given the credentials gap.

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 13-param, no-required-param, no-output-schema mutation tool, this covers the two hardest parts (create vs update, and credentials per kind) plus a merge gotcha. Largely complete; it does not mention default case resolution or the response shape, though those are minor here.

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?

Schema coverage is 100%, but the credentials object is deliberately generic in the schema ('composition depends on the service — see tool description'), and the description supplies that per-provider key map (gigachat authorization_key/scope, yandexgpt api_key/folder_id, custom base_url, etc.). That is real added meaning beyond the schema, though the create-vs-update 'provider' semantics could be tied more tightly to the parameter.

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?

States a specific verb+resource (podklyuchit/nastroit ИИ-сервис) and precisely distinguishes the two modes: create without provider, update with it. An agent can tell it apart from siblings ai_list, ai_delete, ai_test 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?

Explicitly explains the provider parameter's role in selecting create-vs-update, which is the key decision. However it does not name when to reach for ai_test or ai_list instead, so it stops short of full alternative routing.

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