PR-CY MCP

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

Input Schema

Name	Required	Description	Default
`project_id`	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

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and provides almost nothing: 'Получить' implies a read, but it never states that the operation is non-mutating, what happens if the project doesn't exist or isn't owned by the caller, or whether access is permission-scoped. Only the mere fact of retrieval is conveyed.

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?

A single front-loaded sentence with zero filler; nothing needs trimming. Its brevity borders on under-specification, but that is penalized in the other dimensions, not here.

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?

A one-parameter read lookup with complete schema coverage and an output schema, so return values need not be explained. The notable gap is the missing safety/permission context that the absent annotations would otherwise have supplied.

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% — project_id is typed as an integer with exclusiveMinimum 0 and its own description. The description adds only that the lookup is 'по идентификатору', which the schema already establishes, so the baseline of 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 states a specific verb and resource ('Получить проект пользователя') and constrains it to lookup by identifier. It is distinguishable from get_user_projects and get_user_project_by_domain only implicitly, via the 'по идентификатору' phrasing, not by an explicit contrast.

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

Usage Guidelines3/5

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

There is no explicit when/when-not guidance, but 'по идентификатору' implies this is the lookup path when you hold a numeric project ID rather than a domain (the sibling get_user_project_by_domain). Usage is inferable, not stated.

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?