Skip to main content
Glama

Партнёрская программа

get_partner_program
Read-onlyIdempotent

Возвращает партнёрскую статистику текущего пользователя: баланс к выплате и удержанное, список пришедших по партнёрской ссылке с числом их оплат, начисления за период и метки источников. Отвечает на «сколько я привёл и сколько заработал». Только чтение: заявка на выплату и платёжные реквизиты остаются в партнёрском кабинете.

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": "get_partner_program"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько приглашённых вернуть, по умолчанию 20, максимум 200.
date_toNoКонец периода в формате ГГГГ-ММ-ДД.
date_fromNoНачало периода в формате ГГГГ-ММ-ДД. Без него берутся все записи.
source_idNoID метки источника — показать только пришедших по ней.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description reinforces read-only and adds the useful scope boundary that payout operations live elsewhere, but says nothing about result volume, ordering, or what happens when date_from is omitted.

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 short clauses, each doing distinct work: what is returned, the question it answers, and the read-only boundary. Front-loaded with the payload and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by enumerating the returned data groups, and all four optional parameters are fully documented in the schema. Annotations plus the read-only caveat leave no ambiguity an agent would need resolved before calling it.

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%, so every parameter (limit, date_from, date_to, source_id) is already documented with defaults and formats, making the baseline 3 appropriate. The description only implicitly gestures at these via 'начисления за период' and 'метки источников', adding no syntax or interaction detail beyond the schema.

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 gives a specific verb and resource ('Возвращает партнёрскую статистику текущего пользователя') and enumerates the concrete payload: payout/withheld balance, referrals with payment counts, period accruals, and source labels. It scopes the data to the current user, which separates it from a management tool, but it never names a sibling or the write-side counterpart explicitly.

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?

It anchors usage to a concrete question ('сколько я привёл и сколько заработал') and states an explicit exclusion: payout requests and payment details stay in the partner cabinet, so the agent knows this tool will not perform them. It stops short of naming an alternative tool for those actions.

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