PR-CY MCP

get_metrika_mobile_vs_desktop

Сравнить метрики трафика и вовлечённости между мобильными и десктопными пользователями из Яндекс.Метрики. Если даты не указаны, возвращаются данные за последние 7 дней.

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_metrika_mobile_vs_desktop"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Список метрик, по которым осуществляется сортировка.
`limit`	No	Количество результатов для возврата (максимум 100)
`date_to`	No	Дата окончания периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`date_from`	No	Дата начала периода в формате YYYY-MM-DD или значения: today, yesterday, ndaysAgo.
`project_id`	Yes	Идентификатор проекта.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It usefully discloses that missing dates default to the last 7 days, but it does not state that the operation is read-only, nor does it mention permissions, data granularity, or other operational constraints.

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?

Two sentences, front-loaded with the core comparison and followed by the default date behavior. No unnecessary wording or repetition.

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 a full input schema and an output schema present, the description covers the essential purpose and the key default-date behavior. It is somewhat incomplete in not clarifying read-only semantics or sibling alternatives, but it is sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 defines all five parameters. The description adds meaningful behavior by explaining that date_from and date_to default to the last 7 days when omitted, which the schema does not state.

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?

States a specific comparison action and resource: traffic and engagement metrics for mobile vs desktop users from Yandex.Metrika. It is clear what the tool does, but it does not explicitly distinguish itself from other Metrika reporting siblings.

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?

The comparison context implies when the tool is useful, but it does not state when to use it instead of related Metrika tools such as get_metrika_visits or get_metrika_data_by_time. The default-date behavior is helpful but is not usage selection guidance.

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?