Skip to main content
Glama

Состояние своего домена

get_workspace_domain_status
Read-onlyIdempotent

Возвращает свой домен или поддомен аккаунта и состояние его сертификата. Только чтение: привязка домена — это правка DNS на стороне владельца. Нужен, когда публичная ссылка не открывается: чаще всего домен привязан, а сертификат ещё не выпущен. При certificate_state = fail поле certificate_error ({code, message}) говорит, что исправить: message — готовый текст для пользователя; код internal — проблема на стороне сервиса, DNS менять не нужно.

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>"
    },
    "name": "get_workspace_domain_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly and idempotent, but the description adds genuine behavioral context: the rationale for read-only, the diagnostic purpose, the meaning of certificate_state = fail, the shape of certificate_error as {code, message}, and the actionable rule that code internal means a service-side problem where DNS should not be touched. That is operationally useful information the agent cannot get from the structured fields.

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?

Four short sentences, each carrying distinct payload: what it returns, why it is read-only, when to reach for it, and how to interpret an error. The diagnostic trigger is front-loaded right after the purpose statement with no filler.

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 carries the burden of explaining returns, and it does so for the two fields that matter (certificate_state and certificate_error) including their structure. It omits the remaining fields of the domain object and shows only the fail branch, but the gaps are minor for a single-parameter diagnostic tool.

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 coverage is 100% and the single workspace_id parameter is already documented in the schema as coming from workspace://list. The description adds no further meaning about the parameter, 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 opens with a specific verb and resource: it returns the account's own domain or subdomain plus its certificate state. It implicitly separates itself from the domain-mutation sibling by noting that binding a domain is a DNS edit on the owner's side, though it never names manage_workspace_domain, so the differentiation is inferential rather than explicit.

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?

It gives a concrete trigger: use it when a public link does not open, since the usual cause is a bound domain whose certificate has not been issued yet. It also excludes write behavior by stating the tool is read-only and that DNS changes happen on the owner's side. No alternative tool is named, which keeps it short of a 5.

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