Skip to main content
Glama
yandex-wordstat-mcp

yandex-wordstat-mcp

regions_distribution

Read-only

Maps regional interest for a search phrase over the last 30 days using affinity scores, helping identify areas with above- or below-average search volume.

Instructions

Where people search for a phrase over the last 30 days. affinity_index > 100 means the region searches for it more than average, < 100 less.

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": {
      "phrase": "<phrase>"
    },
    "name": "regions_distribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, sorted by count.
phraseYesSearch phrase, Wordstat operators allowed.
devicesNoDevice filter. Omit for all devices.
region_typeNocities = cities only, regions = federal subjects, all = every level.regions

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two genuinely useful behavioral facts not in the annotations: the fixed 30-day lookback (not configurable via any parameter) and the interpretation rule for affinity_index above/below 100. It does not discuss ordering, pagination beyond the schema's limit, or how many regions come back by default.

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?

Two short sentences, front-loaded with the core purpose, followed by the one non-obvious interpretation rule. Nothing is redundant and no filler is present, though the second sentence could be tied more tightly to the first.

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?

With an output schema, full parameter documentation and safety annotations, the description only needs to cover the gaps: it does explain the time window and affinity_index, but says nothing about result ordering, region naming, or how region_type choices change the output granularity, which matters for a distribution 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 description coverage is 100% and each of the four parameters carries its own description (limit, phrase, devices, region_type with enum meanings), so the schema does the heavy lifting. The description mentions no parameter at all, offering nothing beyond the schema baseline.

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 resource and scope: geographic distribution of searches for a phrase within a fixed 30-day window. It is clear on its own, but it never names or contrasts with siblings such as find_region or dynamics, so an agent must infer the distinction from names alone.

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 explicit when-to-use statement, no when-not-to-use condition, and no named alternative. The only guidance-like element is the implicit 'over the last 30 days' scope, which tells the agent the data recency but not when this tool beats find_region or top_requests.

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