Crawlora MCP

yandex_suggest

Read-only

Returns Yandex search-box autocomplete completions for a query prefix in Yandex's own ranking order. Use for Russian-language keyword ideas; accepts an optional two-letter UI language such as en, ru, or tr.

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": {
      "q": "<q>"
    },
    "name": "yandex_suggest"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search query prefix to autocomplete. Required, e.g. openai.
`lang`	No	Two-letter Yandex UI language such as en, ru, or tr, default en. Yandex ignores codes it does not support.
`count`	No	Suggestions to return, default 10, clamped to 1..20.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds one useful behavioral detail (results in Yandex's own ranking order) and notes that unsupported language codes are ignored, but doesn't elaborate on response shape or limits.

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 tight sentences, zero filler, with the core purpose and ordering behavior front-loaded before the usage hint. Every clause earns its place.

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 an output schema present, return values need no explanation, and all three parameters are documented in the schema. The description covers purpose, language handling, and ranking order, leaving only minor gaps like rate/limit context.

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 q, lang, and count are already documented with defaults and clamps. The description restates the optional two-letter UI language but adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 (Returns) and resource (Yandex search-box autocomplete completions) scoped to a query prefix, with the added detail that results follow Yandex's own ranking order. This is clearly distinguishable from yandex_search, though it does not name that sibling explicitly.

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?

Gives a clear use context ('Use for Russian-language keyword ideas'), which tells the agent when this tool is appropriate. It stops short of naming alternatives or stating when-not to use it, so it falls just below the explicit routing bar.

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

All Crawlora 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?