Skip to main content
Glama

MyTender — Kazakhstan tenders

Найти тендеры

search_tenders
Read-only

Открытые лоты (идёт приём заявок) по словам из названия, региону, сумме, типу и площадке. Возвращает до 20 лотов: id, название, заказчик, сумма, регион, способ, срок, ссылка. Закупки из одного источника и среди организаций инвалидов скрыты.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoПорядок: новые, скоро конец приёма, крупные
limitNoСколько лотов вернуть, 1–20 (по умолчанию 10)
queryNoСлова из названия лота, номер лота или объявления, например «ноутбук» или «услуги охраны»
regionNoРегион: Астана, Алматы, Шымкент или область, например «Карагандинская обл.»
categoryNoТовары, работы или услуги
platformNoПлощадка; по умолчанию goszakup
amount_toNoСумма лота до, ₸
amount_fromNoСумма лота от, ₸
price_requests_onlyNoТолько запросы ценовых предложений (ЗЦП)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "goszakup",
      -  "samruk",
      -  "mitwork",
      -  "all"
      -]New value: +[
      +  "goszakup",
      +  "samruk",
      +  "mitwork",
      +  "tizilim",
      +  "all"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description's added value here is the disclosure that single-source procurements and disabled-persons'-organization procurements are hidden from results — a material scope limitation an agent could not learn from the schema. The 20-lot cap is also stated, though pagination beyond that cap is not addressed.

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?

Three tightly packed sentences: purpose and filter scope first, return payload second, exclusions last. Nothing is redundant and the front-loaded purpose sentence lets an agent make a selection decision immediately.

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?

With nine optional parameters, no output schema, and no required fields, the description carries the right load — it names the return fields that the missing output schema would otherwise supply and flags hidden data. The only gaps are pagination behavior past the 20-lot ceiling and whether applying no filters returns a default set.

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% and every parameter, including all three enums, carries its own documentation, so the schema does the heavy lifting. The description only corroborates the filter axes already described in the schema and adds no format details, defaults, or interaction rules beyond it.

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 names a specific operation (open lots currently accepting applications) filtered by five concrete axes — title keywords, region, amount, type, and platform — which cleanly separates it from the sibling retrieval tools get_tender, get_customer, and price_history. It also states the return shape (up to 20 lots with id, title, customer, amount, region, method, deadline, link).

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

Usage Guidelines3/5

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

Usage context is implied by the filter list: an agent can infer this is for discovery when it has keywords, a region, or an amount range rather than a known tender id. However, the description never states when NOT to use it or explicitly routes to siblings like get_tender for a specific lot or price_history for past pricing, leaving the choice to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources