Yandex Lavka Uzbekistan MCP

Overview Schema Source Related Servers Discussions Admin

delivery_location

Set delivery coordinates (country, latitude, longitude) for subsequent grocery search, cart, and checkout calls without changing account or server state.

Instructions

Choose coordinates for subsequent calls; no account or server state is changed.

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": {
      "country": "<country>",
      "longitude": "<longitude>",
      "latitude": "<latitude>"
    },
    "name": "delivery_location"
  }
}

Input Schema

Name	Required	Description	Default
`country`	Yes
`latitude`	Yes
`longitude`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

B3.3/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 that no account or server state is changed, but it does not explain session persistence, validation behavior, or whether this overrides saved addresses.

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 a single front-loaded sentence with no wasted wording. It communicates the core action and the non-mutating behavior efficiently.

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 three-parameter setter, the description covers the high-level purpose and non-mutation. It remains incomplete because the required parameters are undocumented and the relationship to sibling location tools is not clarified.

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?

Schema description coverage is 0%, so the description must compensate for three undocumented required parameters. It only mentions "coordinates," loosely covering latitude and longitude, and says nothing about country, formats, ranges, or expected values.

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 action, choosing coordinates, and clarifies that it affects subsequent calls. It does not distinguish this tool from siblings such as detect_delivery_location or suggest_address, so sibling differentiation is missing.

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?

The phrase "for subsequent calls" implies this should be used before operations that need a delivery location. However, it gives no explicit when-not guidance and does not name alternatives for detecting or selecting a location.

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