Skip to main content
Glama

Krasoft Russian Public Procurement

by ru.krasoft

Срез рынка по коду

market_snapshot
Read-only

Агрегированный срез рынка госзакупок по коду классификатора: kind=okpd2 — категория ОКПД2 (напр. "21.20.10"), kind=ktru — позиция каталога КТРУ, kind=mnn — лекарство по МНН (slug латиницей с zakupki.krasoft.ru, напр. "ibuprofen"). Возвращает счётчики закупок и контрактов, суммы, тренд по годам, топ-заказчиков/регионов. Без товарных цен — те доступны на платном тарифе через search_purchase_objects/search_contract_specs. Квоты: аноним — 20 поисков и 50 карточек в сутки; бесплатный аккаунт (ключ krsp_ с zakupki.krasoft.ru/me) — 100 поисков и 200 карточек; платный тариф — без лимитов. При превышении инструмент вернёт isError с инструкцией.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesКод ОКПД2 / код КТРУ / slug МНН
kindYesТип кода: okpd2 — классификатор продукции, ktru — каталог товаров/работ/услуг, mnn — лекарство по МНН

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true. Description adds details: returns counters, sums, trends, top customers/regions; no item prices; quota limits; error behavior. No contradiction.

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?

Single paragraph of 4-5 sentences, front-loaded with main purpose, then explains parameters, distinguishes from siblings, and adds quotas. Every sentence is informative without fluff.

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 tool with 2 params, full schema coverage, no output schema, and annotations, the description is complete. It explains return types, trade-offs (no prices), and quota handling.

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%, but description adds context: examples of OKPD2 code (21.20.10), MNN slug (ibuprofen from zakupki.krasoft.ru), and explains how kind values map to code formats. This enriches 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 states the tool returns an aggregated market snapshot for government procurement by classifier code (OKPD2, KTRU, MNN). It also mentions what it does NOT return (item prices) and distinguishes itself from sibling tools.

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?

Explicitly states when to use (get aggregated counters, sums, trends, top customers/regions) and when not (if need item prices, use the other tools). Also provides quota limits for different account types and behavior when quotas exceeded.

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 toolsInspect
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