Skip to main content
Glama

MyTender — Kazakhstan tenders

Заказчик и конкуренты

get_customer
Read-only

Заказчик по БИН за 12 месяцев: сколько лотов и сколько не состоялось, заявок на лот, обычная скидка победителей, как платит по актам, главные поставщики, «свой» поставщик, рейтинг 0–100.

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": {
      "bin": "<bin>"
    },
    "name": "get_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
binYesБИН заказчика, 12 цифр

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 the safety and openness profile is covered. The description adds useful scope by specifying a 12-month window and enumerating the analytics returned, including 'как платит по актам' and '«свой» поставщик'. It does not disclose freshness, source, rate limits, or output structure, so it adds context but remains limited.

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?

The definition is a single front-loaded sentence that names the resource, key identifier, time window, and returned analytics. Every listed item contributes to understanding what the tool returns, with no filler or repetition. The compact list format is appropriate for a data-profile tool.

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-only analytics lookup with no output schema, the description does the necessary work by listing the main returned metrics and the 12-month scope. It is complete enough to call correctly, but it does not describe output shape, edge cases, or data limitations. A 4 reflects strong coverage with minor remaining gaps.

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?

There is one required parameter, bin, and schema description coverage is 100%, with the schema already stating that it is a 12-digit customer BIN. The description reinforces the BIN-based lookup and 12-month scope but adds no new syntax, formatting, or validation meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly identifies the resource as a customer profile retrieved by BIN and scopes it to a 12-month window. It lists concrete analytics such as lots, failed lots, bids per lot, winner discounts, payment behavior, suppliers, and a 0–100 rating. It does not explicitly distinguish this from siblings like get_tender, price_history, or search_tenders, so it falls short of a 5.

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 is implied by the phrase 'Заказчик по БИН за 12 месяцев' and the analytic fields listed, suggesting it is for customer-level analysis rather than tender search or price history. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives. This is adequate but leaves routing 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