Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

partner_link

Creates a partner referral link for an external account so referred customers can be tracked, with optional destination URL and dry-run preview.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNo
destination_urlNo
external_account_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/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 it discloses nothing: no indication of whether a link is created or merely retrieved, whether the call mutates state, what dry_run implies, or what authorization the external_account_id requires. For a tool whose schema includes a dry_run flag — implying a mutating default — this silence is a serious gap.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than conciseness: a single fragment with no verb, no front-loaded action statement, and nothing that earns its place as guidance. The one informative clause explains the concept rather than the operation.

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 for a tool with a required account identifier and a dry_run mode the definition should at minimum state the operation and the effect of dry_run. Given three undocumented parameters and zero annotations, the description leaves the agent without enough to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, including a required external_account_id, an optional destination_url, and a dry_run boolean. The description mentions none of them and adds no meaning about formats, defaults, or effects, leaving the agent to infer everything from terse property names.

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

Purpose2/5

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

The description is a noun phrase gloss ('partner link: clients come through it') that restates the tool name rather than naming an operation. It explains what a partner link conceptually is but never says whether the tool creates, fetches, or resolves one, so an agent cannot tell what action it performs.

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 guidance, no prerequisites, and no mention of the sibling tools (claim, referral_status, member) that might otherwise be candidates. The one clause about clients arriving via the link implies a referral context but stops short of a usage rule.

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