citilink-mcp

find_markdown

Read-onlyIdempotent

Search Citilink markdown and used ('Уценка', '(Б/У)') products by category or product ID in a city, revealing discounted price, reason, condition, warranty, and pickup availability.

Instructions

Markdown and used units («Уценка», "(Б/У)") in a city: by category, or copies of one product.

Per item: price, strikethrough price, why it is marked down, completeness, wear, damage, warranty (often 1 month), the id of the new product, units in the area's stores and the earliest pickup date. Store-level detail: get_product with the M-id. Plain search rarely shows these items.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	City: id ('ekat_cl', 'ekat_cl:5x0029236') or name ('Екатеринбург', 'Кировск, Мурманская'). Default: CITILINK_CITY, else Екатеринбург
`page`	No	Page (48 per page), category mode only
`sort`	No	Order, category mode only	price_asc
`product`	No	Instead of a category: a product id/URL — lists markdown units of exactly this product
`category_slug`	No	Category slug, e.g. 'noutbuki' or 'holodilniki' (the `slug` in search_products categories)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only and idempotent behavior, so the description does not need to repeat that. It adds useful behavioral context by describing the item-level data included, the relationship to the new product id, and the fact that these items are not usually visible in plain search.

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 compact and well-organized: it opens with the core purpose, then lists the per-item details, and closes with routing guidance. Every sentence contributes useful information without redundancy.

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?

Given the rich input schema, output schema, and annotations, the description provides enough context for an agent to select and invoke the tool correctly. It covers the main use cases, the distinction between category and product modes, and the relationship to get_product.

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 coverage is 100%, so parameters are already documented well. The description adds meaning by clarifying the two search modes (category vs. product copies) and by explaining how the M-id relates to get_product, which goes beyond the raw parameter descriptions.

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 states that the tool finds markdown and used units in a city, organized by category or by copies of one product. It distinguishes itself from plain search and names get_product for store-level detail, so an agent can tell exactly what this tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use this tool for markdown/used units and when to switch to get_product for store-level detail. It also notes that plain search rarely shows these items, reinforcing the appropriate context for this tool over alternatives.

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

Deploy Server