Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yandex_suggest

Fetch Yandex search-box autocomplete suggestions for a query prefix, ranked by Yandex, with optional language and count.

Instructions

Suggest Yandex search queries. Returns Yandex search-box autocomplete completions for a query prefix, in Yandex's own ranking order. lang is the two-letter Yandex UI language (en, ru, tr, ...) and re-ranks the list; Yandex ignores codes it does not support.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query prefix
langNoTwo-letter Yandex UI language, such as en, ru, or tr; defaults to en
countNoSuggestions to return; defaults to 10, clamped to 1..20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that results are returned in Yandex's own ranking order and that the `lang` parameter re-ranks the list while unsupported codes are ignored, but it omits other behavioral details such as read-only nature, rate limits, or error handling.

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?

The description is three sentences, front-loads the core purpose, and every sentence adds useful information. There is no redundant or filler content.

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 three-parameter autocomplete tool with no output schema and no annotations, the description is nearly complete: it explains the return semantics and the `lang` behavior. It does not mention the default or clamping behavior of `count`, but the schema already covers that, so the gap is minor.

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 baseline is 3. The description adds value beyond the schema by explaining that `lang` is the two-letter Yandex UI language that re-ranks the list and that unsupported codes are ignored, which clarifies the parameter's behavioral effect.

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 verb and resource: 'Suggest Yandex search queries' and specifies that it returns 'Yandex search-box autocomplete completions for a query prefix.' This clearly distinguishes the tool from yandex_search, but it does not explicitly name any sibling tool or alternative, so it falls short of full sibling differentiation.

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?

The description explains what the tool returns but offers no explicit guidance on when to use it versus alternatives like yandex_search, yahoo_search_suggest, or google_suggest. There is no when-not guidance and no prerequisites are mentioned.

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

Deploy Server

Other Tools