Skip to main content
Glama

Link to the right cabinet page

dosai_get_cabinet_link
Read-onlyIdempotent

The ONLY source of links to the cabinet: an address composed from memory does not open, so call this tool every time a link is needed. A direct dosai.pro link to a cabinet page, for what is done by hand there (WhatsApp by QR, paying by card, uploading a file to the knowledge base or a price list file, the Kaspi cash desk, invoices and refunds, deleting the project) or what the owner wants to see with his own eyes. Give the link and say in one sentence which button to press. Places: channels (Подключить WhatsApp: по QR (сканирует владелец телефоном, на котором стоит WhatsApp бизнеса) или официально через Meta (вход в Facebook; номер из WhatsApp Business или SIM без WhatsApp). Посмотреть каналы, добавить карту в Meta, фото профиля номера.); top_up (Пополнить баланс проекта: платит владелец сам, картой или Kaspi.); team (Команда проекта: кто что видит.); broadcasts (Рассылки: посмотреть, продолжить остановленную.); knowledge (Загрузить файл (Excel, PDF, Word) в базу знаний или файл прайса.); functions (Функции бота: посмотреть, тонко настроить колонки таблицы или цепочку; уведомление от своего Telegram-бота с его ключом.); integrations (Интеграции: amoCRM, Битрикс24, U-ON, iiko, Altegio, YCLIENTS и своя программа; ключи и пароли владелец вводит здесь сам.); payments (Подключить кассу Kaspi, счета клиентам, возвраты.); notifications (Уведомления владельцу: куда и о чём, свои тексты.); reports (Отчёты по расписанию: собрать свой отчёт из блоков, посмотреть прошлые.); test_chat (Поговорить с ботом самому, как клиент.); bot_settings (Описание бота и все настройки.); delete_project (Удалить проект целиком (необратимо, только владелец).)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "place": "<place>"
    },
    "name": "dosai_get_cabinet_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / place / enum
      Previous value: -[
      -  "channels",
      -  "top_up",
      -  "team",
      -  "broadcasts",
      -  "knowledge",
      -  "functions",
      -  "payments",
      -  "notifications",
      -  "reports",
      -  "test_chat",
      -  "bot_settings",
      -  "delete_project"
      -]New value: +[
      +  "channels",
      +  "top_up",
      +  "team",
      +  "broadcasts",
      +  "knowledge",
      +  "functions",
      +  "integrations",
      +  "payments",
      +  "notifications",
      +  "reports",
      +  "test_chat",
      +  "bot_settings",
      +  "delete_project"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  3. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed 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)$"
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses on behavior that the annotations cannot convey: links cannot be assembled from memory because such addresses will not open. That is a genuinely useful operational trait. It adds no auth or rate-limit detail and does not say what the return looks like beyond 'a direct dosai.pro link'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key rule is front-loaded in the first sentence, which is good. The remainder, however, is one dense run-on paragraph of parenthetical page details in mixed Russian and English, which is hard to scan; some sub-clauses (button labels, 'фото профиля номера') go beyond what is needed to select an enum value.

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 two parameters, no output schema, and annotations covering the safety profile, the description gives enough to call the tool correctly: it names the return value, explains why the tool must be used, and fully documents the enum. The only real gap is whether the specialized WhatsApp-link sibling should be preferred for that one case.

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

Parameters5/5

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

Schema description coverage is only 50%, since project_id is documented but the place enum is not. The description compensates fully by enumerating all thirteen enum values and explaining, in owner-facing terms, what each page is for (e.g. top_up = the owner pays by card or Kaspi; delete_project = irreversible and owner-only). An agent can pick the right `place` directly from the description.

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 returns a direct dosai.pro link to a named cabinet page. The claim 'The ONLY source of links to the cabinet' makes the tool's role unambiguous. It stops short of explicitly separating itself from the sibling dosai_get_whatsapp_connect_link, which covers overlapping ground via the 'channels' place.

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?

The description gives clear context for when to use the tool ('call this tool every time a link is needed') and explicitly rules out the alternative of constructing the address by hand ('an address composed from memory does not open'). It also adds a delivery instruction ('Give the link and say in one sentence which button to press'). It does not address when to use the WhatsApp-specific sibling link tool instead.

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