Yandex Wordstat MCP

Get Region Children

get-region-children

Retrieve child regions for a given region ID to drill down into the geographic hierarchy. Use with depth parameter to control detail level.

Instructions

Returns the children of a specific region. Use to drill down from get-regions-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": {
      "regionId": "<regionId>"
    },
    "name": "get-region-children"
  }
}

Input Schema

Name	Required	Description	Default
`depth`	No	Depth of children to return (1-3, default: 2)
`regionId`	Yes	Region ID to get children for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only says 'returns the children' without explaining behavior like pagination, error handling, or the effect of the depth parameter (which is only documented in schema). This is insufficient for a tool with no annotation safety net.

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, no fluff. Front-loaded with purpose, then usage tip. Every word earns its place.

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?

For a simple two-parameter tool with no output schema, the description is adequate but incomplete. It does not describe the return format (e.g., list of region objects) or clarify nested behavior (depth implies recursion). Could be more thorough.

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?

Input schema has 100% description coverage, so the schema already explains both parameters (regionId, depth with min/max). The description adds no extra semantics beyond what's in the schema, earning a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns children of a specific region (verb 'Returns', resource 'children of a specific region'). It distinguishes itself from the sibling 'get-regions-tree' by advising to use this for drilling down after that call.

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?

The description provides a clear usage context: 'Use to drill down from get-regions-tree.' It implies this tool is for subsequent navigation, but does not explicitly exclude other scenarios or mention when not to use it.

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

Deploy Server