Skip to main content
Glama

MyTender — Kazakhstan tenders

Карточка лота

get_tender
Read-only

Всё о лоте по его id (из search_tenders или ссылки mytender.kz/tenders/): характеристики, предоплата, срок поставки, документы, число поданных заявок, рейтинг заказчика, оценку шанса и обычной цены победы по похожим закрытым лотам (без ИИ) и ИИ-разбор ТЗ (если его уже запускали на MyTender).

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": {
      "id": "<id>"
    },
    "name": "get_tender"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid лота MyTender (число из ссылки mytender.kz/tenders/<id>)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: the win-chance and price figures are computed from similar closed lots without AI, and the AI spec breakdown is only present if it was previously launched on MyTender — a conditional-availability detail an agent could not infer. Nothing about failure modes (unknown id) or auth is given.

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?

One front-loaded sentence: the action and the id source come first, the payload enumeration follows. The dense list earns its place because there is no output schema to describe the return value, and there is no filler.

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 one-parameter read tool with no output schema, the description carries the return-value burden well by naming every included section and flagging that the AI analysis is conditional. It lacks only what happens when the id is invalid or how large/expensive the response is.

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% and the single id parameter is already documented as the number from mytender.kz/tenders/<id>. The description largely repeats that, adding only the alternate source (search_tenders) — marginally useful, but no format, range, or edge-case semantics beyond 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?

States a specific verb+resource ('Всё о лоте по его id') and enumerates the exact payload: characteristics, prepayment, delivery term, documents, bid count, customer rating, win-chance estimate, typical winning price, and AI spec analysis. It also names the sibling search_tenders as the id source, so an agent can tell it apart from the list tool without opening a schema.

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?

Usage context is clear: call this for a single lot after finding its id in search_tenders or from a mytender.kz/tenders/<id> link. There are no explicit exclusions (e.g. when to prefer get_customer for the customer rating that is also returned here), so it stops short of full when/when-not guidance.

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