Skip to main content
Glama

Свой домен аккаунта

manage_workspace_domain
Destructive

Адрес, по которому открываются опросы аккаунта: служебный адрес сервиса, поддомен аккаунта или свой домен. Инструмент показывает текущее состояние вместе с состоянием сертификата, задаёт поддомен и переключает используемый адрес. Подключение своего домена сюда не входит: там нужна правка DNS на стороне владельца и выпуск сертификата с недельным лимитом на повторы — это делают в кабинете. Адрес отдельного опроса внутри домена меняет set_quiz_link.

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": {
      "workspace_id": "<workspace_id>",
      "action": "<action>"
    },
    "name": "manage_workspace_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: show — текущее состояние, set_subdomain — задать поддомен, set_type — переключить используемый адрес.
subdomainNoИмя поддомена. Обязателен для set_subdomain; чтобы убрать поддомен, передайте пустую строку.
domain_typeNoКакой адрес использовать: default — служебный, subdomain — основной поддомен, other_subdomain — дополнительный, domain — свой домен. Обязателен для action=set_type.
workspace_idYesID workspace. Взять из workspace://list.
subdomain_kindNoКакой поддомен задаём: default — основной, other_subdomain — дополнительный.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, and the description adds useful context about certificate state and the weekly certificate retry limit that explains why domain connection is out of scope. However, it never warns that switching domain_type can break already-published survey links, which is exactly the kind of consequence an agent needs when destructiveHint is true and the operation is not idempotent.

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

Conciseness5/5

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

Three sentences, front-loaded with the scope definition, then capabilities, then exclusions. Every clause carries information; no restatement of the title or the enum values.

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 five-parameter mutation tool with a fully documented schema and no output schema, the description covers purpose, scope boundaries, and the sibling handoff. It falls short only on the consequences of set_type and on disambiguating itself from get_workspace_domain_status.

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 all three enums are fully documented in the schema, including the empty-string convention for removing a subdomain. The description adds essentially nothing parameter-level beyond the schema, so the baseline of 3 applies.

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?

The description names the resource precisely (the address at which account surveys open) and enumerates the three address kinds, then lists the concrete verbs: shows current state with certificate state, sets a subdomain, switches the address in use. It also carves out what the tool does NOT do (custom domain connection) and names a sibling, set_quiz_link, for per-quiz addresses.

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?

Clear exclusions are stated: connecting a custom domain requires DNS changes and certificate issuance with a weekly retry limit, so it happens in the dashboard, and per-quiz paths go to set_quiz_link. The gap is that the description never distinguishes this tool's action=show from the sibling get_workspace_domain_status, which by name alone appears to overlap on the status-reading case.

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