Krasoft Russian Public Procurement

Поиск товарных позиций извещений

search_purchase_objects

Read-only

Поиск по товарным позициям извещений (одна строка = один объект закупки: наименование, код и категория ОКПД2, количество, цена за единицу, сумма) с данными родительского извещения (заказчик, регион, НМЦК, победитель). Это уровень товара, а не закупки целиком — подходит для вопросов «кто и почём закупает конкретный товар». На бесплатных тирах значения цен/количеств и поставщики замаскированы (тизер) — полные данные на тарифе «Отраслевой». Квоты: аноним — 20 поисков и 50 карточек в сутки; бесплатный аккаунт (ключ krsp_ с zakupki.krasoft.ru/me) — 100 поисков и 200 карточек; платный тариф — без лимитов. При превышении инструмент вернёт isError с инструкцией.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fz`	No	Закон: 44 и/или 223
`page`	No	Страница выдачи (0-based)
`query`	No	Текст поиска по позиции и извещению. Все слова обязательны (AND) и должны встретиться в одном поле, поэтому длинная фраза сужает выдачу — для оценки объёма рынка лучше короткий запрос или okpdCode
`period`	No	Период публикации: "2y" (default) — последние 2 года, "5y" — 5 лет, "older" — старше 5 лет, "all" — весь корпус (медленнее)	2y
`priceTo`	No	Цена за единицу до, руб.
`okpdCode`	No	Код ОКПД2 позиции (префиксный матч, напр. "21.20")
`pageSize`	No	Размер страницы
`priceFrom`	No	Цена за единицу от, руб.
`objectName`	No	Наименование объекта закупки (поиск только по названию позиции)
`regionCodes`	No	Коды регионов РФ: 2 цифры ("77" — Москва) либо полный 13-значный код
`includeTotal`	No	Точный счёт найденного (обрезан 10 000)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 22, 2026

changedInput schema / properties / query / description

Previous value: -"Текст поиска по позиции и извещению"New value: +"Текст поиска по позиции и извещению. Все слова обязательны (AND) и должны встретиться в одном поле, поэтому длинная фраза сужает выдачу — для оценки объёма рынка лучше короткий запрос или okpdCode"

changedInput schema / properties / regionCodes / description

Previous value: -"Коды регионов РФ (2 цифры)"New value: +"Коды регионов РФ: 2 цифры (\"77\" — Москва) либо полный 13-значный код"

First observedJul 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true. Description adds significant behavioral details: free-tier masking (tizer), quota limits (20 searches/50 cards for anonymous, 100/200 for free account, unlimited for paid), and error behavior (isError with instructions on exceeding limits). No contradictions.

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?

Description is concise (few sentences) and well-structured: purpose first, then additional context, limitations, quotas. Every sentence adds value with no 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?

Despite no output schema, the description lists key return fields (name, code, category, quantity, unit price, sum, and parent notice data). Covers data level, tier restrictions, quotas, and error handling. Complete for a search tool with 100% schema coverage.

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% with detailed parameter descriptions. The main description adds extra context: AND logic for query words, advice for market volume estimation, and clarification that search is across both item and notice fields, exceeding baseline.

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?

Clearly states it searches for purchase items (товарные позиции извещений) and distinguishes from tool-level procurement by specifying 'Это уровень товара, а не закупки целиком'. Provides specific use case: 'кто и почём закупает конкретный товар'.

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?

Explicitly describes when to use (item-level product queries) and provides context on data masking and quotas. Does not explicitly name siblings or when not to use, but the context is clear enough.

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

All Krasoft Russian Public Procurement tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct aspect: customer profiles, execution summaries, contract cards, tender cards, market snapshots, and searches for specs, objects, and tenders. No two tools have overlapping purposes.

Naming Consistency4/5

Tool names mostly follow a verb_noun or noun_noun pattern (e.g., search_tenders, get_contract, market_snapshot). However, there is minor inconsistency with 'executions_summary' and 'market_snapshot' not using a verb prefix like the others.

Tool Count5/5

With 8 tools, the server covers search, retrieval, and aggregation for public procurement without being overwhelming or too sparse. Each tool serves a clear purpose.

Completeness4/5

The set covers search and retrieval for both tenders and contracts, plus profiles and aggregated summaries. Missing a dedicated supplier search tool, but the overall surface is solid for data access.

Resources

Need Help?