Skip to main content
Glama

MyTender — Kazakhstan tenders

Цены прошлых закупок

price_history
Read-only

Закрытые закупки того же товара по коду КТРУ (ЕНС ТРУ): сумма, цена договора, скидка, победитель; медиана скидки. Можно сузить до заказчика.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ktru": "<ktru>"
    },
    "name": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
ktruYesКод КТРУ, например 262013.000.000018
customer_binNoБИН заказчика — показать ещё, кто у него выигрывал

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value by scoping the data to closed procurements only and noting a computed median discount, but it says nothing about result limits, time coverage, or whether the median is computed over the returned set or the whole market.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource and output fields front-loaded, followed by the narrowing option. Every clause carries information; the semicolon-separated field list is slightly terse but efficient.

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?

For a two-parameter read-only lookup with no output schema, the definition covers scope, expected fields, and the optional customer narrowing, and annotations handle the safety profile. Only secondary details (result caps, time window, sourcing of the median) are absent.

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 coverage is 100%: ktru and customer_bin both carry descriptions, and the description only restates them ('по коду КТРУ', 'сузить до заказчика'). Baseline 3 applies since the schema does the heavy lifting and the prose adds no format or syntax detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (closed procurements of the same good by KTRU/ENS TRU code) and enumerates the returned fields: amount, contract price, discount, winner, median discount. It is immediately clear what the tool returns, though it never contrasts itself with siblings like search_tenders or get_tender.

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?

The final clause ('Можно сузить до заказчика') tells the agent how to narrow results to a customer, which is usable guidance. However there is no explicit when-to-use versus alternatives and no exclusions, so the agent must infer that this is the price-history tool rather than tender search.

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