Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

member

Registers an affiliate program participant and records their referral source with a unique event ID to support attribution and status tracking.

Instructions

Участник программы и от кого он пришёл. eventId уникален навсегда

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": {
      "event_id": "<event_id>",
      "occurred_at": "<occurred_at>",
      "member_id": "<member_id>"
    },
    "name": "member"
  }
}

Input Schema

NameRequiredDescriptionDefault
legNo
statusNoactive
dry_runNo
event_idYes
member_idYes
sponsor_idNo
occurred_atYes
placement_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/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 disclosure burden. It does contribute one genuinely useful behavioral fact, that eventId is permanently unique (implying deduplication/idempotency), but says nothing about whether records are created or mutated, what dry_run does, permission requirements, or reversibility.

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?

Two short fragments with no filler, and the uniqueness constraint is stated compactly. However the terseness crosses into under-specification, and there is no structure separating purpose from behavior.

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

Completeness3/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, which offsets some burden. Against that, an 8-parameter, 3-required tool with zero annotation coverage and a one-line description leaves far too much unresolved for reliable invocation.

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% across 8 parameters, so the description must compensate and largely fails. It explains only event_id's uniqueness invariant, leaving leg, status, sponsor_id, placement_id, occurred_at, and dry_run with no meaning beyond their titles.

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 names an entity ("program member and who they came from") but supplies no verb, so an agent cannot tell whether this tool reads, creates, or upserts a member record. The only addition over the name is the sponsor relation and the eventId note, which restates the resource rather than an operation.

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 indication of when to call this versus siblings such as claim, referral_status, or partner_link, nor any prerequisite or exclusion. The agent must infer usage entirely from the parameter list.

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