Skip to main content
Glama

Top up the balance (the owner pays in Kaspi)

dosai_request_topup
Destructive

Put a Kaspi bill for a balance top-up of $1-1000: method=push sends the bill to the Kaspi app of the given phone, method=qr returns a QR to pay from Kaspi.kz. Money moves only when the owner pays it himself in Kaspi; nothing is charged by this call. For a card, give the cabinet link: dosai_get_cabinet_link with place=top_up.

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": {
      "project_id": "<project_id>",
      "amount_usd": "<amount_usd>",
      "method": "<method>"
    },
    "name": "dosai_request_topup"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoFor push: the owner's Kaspi number, e.g. 77071234567.
methodYes
amount_usdYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds the crucial nuance that "nothing is charged by this call" and money moves only when the owner pays in Kaspi — context the annotations cannot convey. It stops short of saying what happens to an unpaid or expired bill, or whether a pending bill record persists, which is the remaining behavioral gap.

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?

Three tight sentences, front-loaded with the action and the amount range, then mode semantics, then the payment-reality caveat, then the alternative. Dense but every clause carries information; only the sibling pointer could be trimmed slightly.

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 no output schema, the description still tells the agent what each mode yields (a bill pushed to the app vs a returned QR) and that no funds are captured. Missing only edge-case behavior such as bill expiry or what a pending top-up looks like in balance history.

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 only 50% (phone and project_id are documented, method and amount_usd are not), and the description compensates by defining both enum values of method and the $1-1000 bound on amount_usd. It does not restate the phone format, but the schema already covers that.

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 verb and resource ("Put a Kaspi bill for a balance top-up") and immediately disambiguates the two modes: method=push sends the bill to the Kaspi app, method=qr returns a QR. An agent can distinguish this from dosai_get_balance or dosai_get_cabinet_link without opening any schema.

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?

It states the selection rule between the two modes (push vs qr) and explicitly routes the card case to a named sibling: "For a card, give the cabinet link: dosai_get_cabinet_link with place=top_up." That is an explicit when-to-use-this vs when-to-use-alternative instruction.

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