PR-CY MCP

get_position

Получить позицию домена в поисковой системе по одной или нескольким ключевым фразам за один вызов. Возвращает массив позиций по каждой фразе. Если нужно проверить позиции по нескольким фразам — передавайте их все одним вызовом через запятую, а не делайте отдельный вызов на каждую фразу.

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

Input Schema

Name	Required	Description	Default
`top`	No	Количество результатов
`device`	No	Устройство	desktop
`domain`	Yes	Домен
`engine`	No	Поисковая система	google
`region`	No	Идентификатор региона
`keywords`	Yes	Одна или несколько ключевых фраз, разделённых запятыми (например: "купить телефон, купить ноутбук"). Для проверки нескольких фраз передавайте их все одной строкой в одном вызове, а не вызывайте инструмент отдельно для каждой фразы.

Output Schema

Name	Required	Description
`engine`	Yes	Поисковая система
`task_id`	Yes	Идентификатор задачи, по которому открывается её страница
`keywords_positions`	Yes	Список позиций ключевых слов

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns an array of positions per keyword, which is useful, but says nothing about permissions, rate limits, cost, error behavior, or whether the operation is read-only.

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 short and front-loaded with the core action and return shape. The multi-keyword guidance is slightly repeated between the first and third sentences, but the repetition reinforces the key usage constraint without bloating the description.

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?

An output schema exists, so return-value details are not required here. The description covers the essential multi-keyword behavior and the parameter schema covers the rest; the missing piece is sibling differentiation against `check_positions` and `get_serp`.

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 schema already explains all six parameters. The description adds meaningful guidance for the `keywords` parameter (comma-separated phrases, one call), but provides no additional semantics for `top`, `device`, `engine`, or `region`, which is the correct baseline when the schema is rich.

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 names a specific verb+resource: retrieving a domain's search-engine position for one or more keywords. It clearly scopes the tool to a single call for multiple phrases, but it does not distinguish this tool from the sibling `check_positions`, which likely overlaps in purpose.

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 an explicit usage rule: pass all keywords in one comma-separated call rather than making separate calls per phrase. However, it does not clarify when to choose this tool over alternatives such as `check_positions` or `get_serp`.

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?