Skip to main content
Glama
atomno-mcp

atomno-mcp-zakupki

search_tenders

Search government tenders by status, region, law type, and price range. Filter results from zakupki.gov.ru to find relevant procurement opportunities.

Instructions

Найти тендеры (44-ФЗ / 223-ФЗ / 615-ПП) по фильтрам в ЕИС zakupki.gov.ru.

Возвращает структурированный массив до 100 объектов на вызов с пагинацией через next_page_token. Все фильтры комбинируются через AND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoколичество объектов в ответе (1–100, default 20).
queryNoсвободный поиск по наименованию объекта закупки.
statusNoстатус тендера ("published", "applications_open", "applications_closed", "in_progress", "completed", "cancelled", "all_active").
regionsNoкоды субъектов РФ ("66" = Свердловская обл., "74" = Челябинская).
law_typeNoсписок из ["44-fz", "223-fz", "615-pp"]; default — оба ФЗ.
platformNoЭТП ("sberbank_ast", "rts_tender", "roseltorg", "tek_torg", "gpb", "rad", "fabrikant", "agz_rt").
smp_onlyNoтолько закупки среди субъектов малого предпринимательства.
ktru_codesNoкоды КТРУ для более точной фильтрации.
okpd2_codesNoкоды ОКПД2 (можно префиксы: "62.0" включит всё под 62.0).
customer_innNoИНН заказчика (10 цифр — юр.лицо, 12 — ИП).
customer_ogrnNoОГРН заказчика (13 — юр.лицо, 15 — ИП).
price_max_rubNo
price_min_rubNo
next_page_tokenNoтокен следующей страницы из предыдущего ответа.
publish_date_toNo
publish_date_fromNo
applications_deadline_toNo
applications_deadline_fromNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description explains pagination (up to 100 objects, next_page_token) and how filters combine (AND). It does not cover rate limits or authentication, but provides sufficient behavioral context.

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 concise with three clear sentences, front-loaded with purpose, and contains no unnecessary information.

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

Completeness4/5

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

Given the complexity (18 parameters, output schema exists), the description covers core behavior: search, pagination, AND combination. It could mention permissions or data freshness but is largely complete.

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 67%, and the description does not add significant parameter-specific details beyond what the schema already provides. Baseline score of 3 is appropriate.

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 the tool searches tenders by filters in EIS, specifying the applicable laws (44-ФЗ, 223-ФЗ, 615-ПП). It distinguishes from sibling tools like get_tender (single tender) and lookup_okpd2 (code lookup).

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 implies usage for filtering tenders but does not explicitly state when to use this tool versus alternatives or provide exclusions. It is clear enough for a search tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/atomno-mcp/mcp-zakupki'

If you have feedback or need assistance with the MCP directory API, please join our Discord server