Skip to main content
Glama
yandex-wordstat-mcp

yandex-wordstat-mcp

find_region

Read-only

Find Yandex Wordstat region IDs by name and return each region’s ID, name, and tree path for filtering keyword data by location.

Instructions

Find Wordstat region IDs by name. Returns id, name and the path in the region tree.

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": {
      "query": "<query>"
    },
    "name": "find_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesPart of a region name, e.g. 'Казань'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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 the safety and external-dependency profile is covered structurally. The description adds only the return shape, which is largely duplicated by the output schema, and says nothing about partial matching, multiple hits, or rate limiting against the external service.

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 action and resource. The second sentence overlaps with the output schema, but it is brief enough that the redundancy costs little.

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?

For a simple two-parameter lookup with an output schema, the description covers what the tool does and what it resolves to. Remaining gaps (matching semantics, limit behavior, language handling) are modest given the tool's low complexity.

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 coverage is 50%: query is documented but limit is not. The description reinforces the key semantic ('by name'), making clear the query is a name fragment for resolution rather than an ID or free-text search. It does not explain that limit bounds the number of returned candidates, leaving that gap.

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 verb and resource: 'Find Wordstat region IDs by name'. It is clearly a lookup tool, distinguishable in kind from the analytics-oriented siblings (dynamics, frequencies, regions_distribution, top_requests), though it never names or contrasts them explicitly.

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?

Usage is only implied by 'by name' and the query example. There is no statement of when to prefer this over regions_distribution, no note that it is a resolution/lookup step before other calls, and no mention of prerequisites such as Wordstat API access.

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