Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

payouts

Retrieves a partner's payment history by member ID, enabling agents to review affiliate earnings records without managing funds.

Instructions

История выплат партнёра

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": {
      "member_id": "<member_id>"
    },
    "name": "payouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost none of it: it never states that the operation is read-only, whether results are paginated or time-bounded, whether the payouts belong to the caller or an arbitrary member, or whether authorization beyond the member id is needed. Only 'history' hints at a non-mutating, retrospective read.

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

Conciseness3/5

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

Three words are certainly not padded, but the brevity is under-specification rather than economy; there is no front-loaded verb or scope statement to anchor the agent. Nothing in the phrase earns priority over the missing information.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be explained, but for a tool keyed on a single undocumented required parameter the description should at minimum say whose payouts are returned and under what conditions. As written, the agent knows only a topic, not the transaction semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter, member_id, has 0% schema description coverage and the description never mentions it, so nothing clarifies whether it is the partner's own id, a lookup key for another partner, or an id type from a sibling tool. The name member_id is self-explanatory enough to avoid a 1, but the description adds no meaning beyond it.

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

Purpose3/5

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

The phrase "История выплат партнёра" does identify a resource (partner payout history) and implies a read/list operation, so the agent can guess what comes back. But it is a bare noun phrase with no verb, is written in a different language than the tool name and schema, and does nothing to separate it from siblings such as refund or claim, which could also surface money movements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no mention of when to prefer this over refund, claim, or status, and no prerequisites or exclusions. The agent must infer entirely from the tool name that this is the historical view of payouts rather than a current-status lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.