Skip to main content
Glama
partna-mcp

partna-mcp

Official
by partna-dev

referral_status

Checks whether a customer account is linked to a referral code and returns the associated code.

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

Input Schema

NameRequiredDescriptionDefault
external_account_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 burden. It implies a read-only lookup but never states that explicitly, nor does it mention permissions, error behavior for unknown accounts, or any side effects. Only the presence of an output schema reduces the need to explain return values.

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?

The description is a single short phrase with no wasted words, but brevity here comes at the cost of under-specification rather than efficient front-loading. It is concise without being informative.

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?

For a lookup tool with no annotations and an undocumented required parameter, the description does too little. The output schema excuses it from explaining return values, but the lack of permission, scope, and parameter context leaves real gaps.

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% for the single required parameter 'external_account_id', and the description never mentions it. The agent gets no clarification on what an external account ID is or where to obtain it, so the description fails to compensate for the schema gap.

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 'Привязан ли клиент и к какому коду' conveys that it checks whether a client is linked to a referral code and which one, so the intent is inferable. However, it is phrased as a question with no explicit verb/resource formulation and no differentiation from siblings such as 'status' or 'partner_link', leaving an agent to guess the exact scope.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no indication of when it would return a negative result. The agent must infer usage purely from the question-like phrasing.

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