Yandex Lavka Uzbekistan MCP

Overview Schema Source Related Servers Discussions Admin

suggest_address

Suggests address options for search queries without changing the account's delivery address. Use it to find valid delivery locations before checkout.

Instructions

Suggest addresses; never changes the account's delivery address.

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": "suggest_address"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the key non-mutating behavior, but it leaves out auth requirements, rate limits, return format, and whether the operation performs a live lookup.

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?

The description is a single front-loaded sentence with no wasted words. The non-mutation disclaimer is placed efficiently after the purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a suggestion tool with no output schema, the description should explain what kind of results are returned. It also does not compensate for the undocumented query parameter, leaving an agent without enough context to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter "query" has 0% schema description coverage. The description implies an address-related query but never explains whether it accepts a partial address, a full address, or another format, adding little beyond the schema title.

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

Purpose3/5

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

"Suggest addresses" states a verb and resource, but "suggest" is vague: it could mean autocomplete, validation, or recommendations. The second clause clarifies that it is not a mutation, but it does not distinguish this from sibling tools like detect_delivery_location or saved_addresses.

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 gives a negative constraint (never changes the delivery address), which implies safe usage for suggestions. However, it provides no positive guidance on when to use this tool versus alternatives such as saved_addresses, delivery_location, or detect_delivery_location.

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