Yandex Lavka Uzbekistan MCP

Overview Schema Source Related Servers Discussions Admin

saved_cards

Lists saved payment cards by masked suffix for the given location coordinates, helping you identify which card to use without selecting one.

Instructions

List available saved cards by masked suffix only; this does not select one.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden; it does disclose that output is restricted to masked suffixes (a meaningful privacy/return-shape detail) and that no selection side effect occurs. It omits authentication requirements and any statement of what happens when no cards are saved.

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?

One compact sentence with the resource and the key caveat front-loaded, no filler. It is arguably too terse for the missing parameter explanation, but every word present earns its place.

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?

Schema coverage is 0% and there is no output schema or annotations, yet the description says nothing about the two required parameters (latitude/longitude) that must be supplied to list cards. An agent cannot infer why a location is needed to enumerate saved cards, or whether results are region-scoped.

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

Parameters5/5

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

Placeholder.

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 gives a specific verb and resource ('List available saved cards') and names what is returned ('masked suffix only'), plus an explicit negative scope ('this does not select one'). It could differentiate further from nearby siblings like checkout_preview or set_cart_item, but the core purpose is unambiguous.

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 clause 'this does not select one' implicitly tells the agent this is a discovery/read step rather than a payment selection, which is useful. However, it never names the alternative tool to use when the agent actually wants to choose or pay with a card, nor states prerequisites such as an authenticated session.

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