PR-CY MCP

get_user_project_by_domain

Получить проект пользователя по домену.

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": {
      "domain": "<domain>"
    },
    "name": "get_user_project_by_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Домен проекта.

Output Schema

Name	Required	Description
`id`	Yes	Идентификатор проекта
`domain`	Yes	Домен проекта
`status`	Yes	Текущий статус проекта
`robot_type`	Yes	Бот, соблюдающий правила robots.txt во время краулер-аудита
`week_report`	Yes	Включён ли еженедельный отчёт по проекту
`crawler_mode`	Yes	Режимы, используемые краулер-аудитом
`date_created`	Yes	Дата и время создания проекта в формате ISO 8601
`ga_connected`	Yes	Подключён ли Google Analytics к проекту
`gsc_connected`	Yes	Подключён ли Google Search Engine к проекту
`wordstat_type`	Yes	Тип сбора Wordstat
`use_robots_txt`	Yes	Следовать ли правилам robots.txt
`metrika_connected`	Yes	Подключена ли Yandex.Metrika к проекту
`crawler_user_links`	Yes	Ссылки, заданные пользователем для краулер-аудита
`crawler_auto_update`	Yes	Включено ли ежедневное обновление краулер-аудита страниц сайта
`initialized_crawler`	Yes	Инициализированы ли функции краулера, такие как crawler_auto_update, requests_per_second, use_robots_txt и robot_type
`requests_per_second`	Yes	Максимально допустимое количество запросов в секунду при краулер-аудите
`webmaster_connected`	Yes	Подключён ли Yandex.Webmaster к проекту
`advanced_auto_update`	Yes	Включено ли ежедневное обновление анализа сайта
`base_analytic_system`	Yes	Основная используемая система аналитики
`initialized_advanced`	Yes	Инициализированы ли расширенные функции, такие как advanced_auto_update, week_report и base_analytic_system
`initialized_keywords`	Yes	Добавлены ли ключевые слова, указаны ли регионы и поисковые системы
`crawler_restrict_rules`	Yes	Правила ограничений для краулера
`ignore_wordstat_region`	Yes	Игнорировать ли регион поиска при сборе Wordstat
`enabled_timeline_events`	Yes	Определяет, какие события таймлайна запускают уведомления. Возможные значения: null (по умолчанию) — уведомления включены для всех событий. [] (пустой массив) — уведомления отключены для всех событий. ["ssl:exist", "sitemap:exist", ...] — уведомления включены только для перечисленных кодов событий.
`allow_subdomains_in_serp`	Yes	Учитывать ли поддомены в результатах SERP
`additional_timeline_events_emails`	Yes	Дополнительные email для уведомлений таймлайна

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It implies a read-only lookup with "Получить", but says nothing about permissions, behavior when the domain is not found, or whether multiple projects can match.

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?

The description is a single front-loaded sentence with no wasted words. It is concise, though its brevity reflects under-specification rather than strong structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained here, and the single lookup parameter is documented. For a simple read tool this is minimally complete, but it lacks sibling disambiguation and error/not-found context important in a large toolset.

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 the single domain parameter is already documented in the schema. The description only says "by domain", which mirrors the schema without adding format, source, or validation details. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a verbatim restatement of the tool name: "get_user_project_by_domain" becomes "Get user's project by domain." It does identify the resource and lookup key, but it adds no distinguishing detail versus siblings such as get_user_project or get_user_projects.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool rather than get_user_project or get_user_projects. The only implied usage is the lookup by domain, which is already evident from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PR-CY MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?