Skip to main content
Glama
SZhukovWork

dns-shop-mcp

by SZhukovWork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_products

Read-onlyIdempotent

Find products on DNS with site-like search: filter by category, price range, and stock status, then get city-specific prices, availability, and ratings.

Instructions

Search DNS like the site does: 24 items per page, sorting, price window, stock filter.

Per item: code, name, short specs, the live city price (with pre-discount price, online-payment discount as a conditional estimate, credit payment), not-sold flag with the last sale price, marketplace seller, availability summary, the card's rating (may merge variants) and DNS's reliability label. DNS narrows every query to one category (resolved_category); total_found_in_category counts only there, other_categories lists the rest. Confirm finalists with get_product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity as on dns-shop.ru ('Екатеринбург', 'Москва', 'Name, Region') or its GUID; default: DNS_CITY or Екатеринбург
pageNoResult page, 24 items per page (fixed by DNS)
sortNoOrder as on the site; 'reviews' = most reviewed firstpopular
queryYesSearch phrase as typed on the site (Russian works best)
categoryNo16-hex category id (from `resolved_category` / `other_categories`); default: the category DNS picks
price_maxNoUpper price bound, rubles
price_minNoLower price bound, rubles
availabilityNoDNS's stock filter: 'any' = site default, INCLUDES products no longer sold; 'on_sale' = everything that can be bought (in stock or to order); 'in_stock' = in a store of the city now; 'today'/'tomorrow'/'later' = to order; 'out_of_stock' = not sold any moreany
with_availabilityNoAlso fetch each item's availability summary (+1 request)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the operation read-only, idempotent, and non-destructive. The description adds substantial behavioral detail beyond that: fixed 24-item pages, conditional price estimates, merged ratings, the resolved_category behavior, total_found_in_category semantics, and the extra request cost of with_availability. No contradiction with annotations.

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 dense but every sentence earns its place: it front-loads the core search behavior, then details per-item fields, category narrowing, and the next step. The colon-list structure makes it scannable without wasted words.

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

Completeness5/5

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

For a complex 9-parameter tool, the description covers the important behaviors: result shape, category resolution, pricing nuances, stock semantics, and the follow-up tool. An output schema exists, so the description does not need to restate return types. The only minor gap is not explicitly covering all sibling alternatives, but the tool is fully usable.

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 the baseline is 3. The description reinforces concepts like price window and stock filter but adds little meaning beyond what the schema already provides. It does not introduce new parameter semantics or clarify formats beyond the schema.

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

Purpose5/5

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

The description clearly identifies the tool as a DNS product search with site-like behavior: pagination, sorting, price window, and stock filter. It also differentiates itself from get_product by stating 'Confirm finalists with get_product', so an agent can distinguish search from detail retrieval.

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?

The description makes clear this is the discovery/search step and explicitly points to get_product as the follow-up for confirming finalists. It does not discuss when to prefer compare_products, get_reviews, or get_price_history, but the core usage context is unambiguous.

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