Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

claim

Links an existing client account to a partner code via external_account_id, enabling affiliate attribution for customers already registered with the owner.

Instructions

Привязать клиента к коду партнёра. Клиент уже зарегистрирован у владельца; external_account_id — его идентификатор там

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": {
      "code": "<code>",
      "external_account_id": "<external_account_id>"
    },
    "name": "claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
dry_runNo
external_account_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 largely drops it: it says nothing about whether the link is idempotent, what happens on a conflict or duplicate claim, what permissions or auth are required, or that failure is possible. The precondition it does state is genuinely useful context, but for a mutation tool with zero annotation coverage this is a significant 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?

Two short sentences, front-loaded with the action and followed by the precondition, with no filler. It is efficient, though the brevity leaves the uncovered dry_run flag unaddressed.

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 values need not be described, but this is an unannotated mutation tool whose dry_run flag, conflict behavior, and permissions are undocumented in both schema and description. An agent could invoke it but would not know how to safely preview or what to expect on failure.

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?

Schema description coverage is 0%, so the description must compensate and it only partly does: it explains external_account_id as the client's identifier at the owner. The 'code' parameter is only indirectly implied, and 'dry_run' — a behavioral switch that changes whether the call mutates state — is never mentioned at all.

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+resource: 'Привязать клиента к коду партнёра' (attach a client to a partner code), which resolves the opaque name 'claim'. It does not differentiate against siblings such as partner_link, which may do something adjacent.

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?

The clause 'Клиент уже зарегистрирован у владельца' implies a precondition and therefore an implied when-to-use (the client must already exist on the partner side). There is no explicit when-not guidance, no mention of what to do if the client is already claimed, and no named alternative among the sibling tools.

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