Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_create_referral_link

Generate a Nobitex referral link with a custom friend commission share and program agenda; requires a user token, not API-key authentication.

Instructions

Create a referral link.

Args: friend_share: Commission share granted to the invited friend. agenda: Referral program/scenario identifier.

Requires a user token; Nobitex does not accept API-key auth for this endpoint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nobitex_create_referral_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
agendaNo
friend_shareNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully states that the endpoint requires a user token and that API-key auth is rejected, which is important operational context. However, it does not describe side effects, whether links are single-use, what the returned link looks like, or any rate limits, leaving significant behavioral gaps for a mutation tool.

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?

The description is short, front-loaded with the purpose, and then documents the two arguments and auth requirement without waste. The Args block is slightly list-like but appropriate for a two-parameter tool.

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?

For a low-complexity tool with two optional parameters and no output schema, the description covers purpose, parameters, and authentication. It still lacks usage guidance relative to sibling referral tools and does not describe the result, which leaves the definition only minimally complete.

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

Parameters3/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 for both parameters. It defines friend_share as the commission share for the invited friend and agenda as a referral program/scenario identifier, which adds meaning beyond the bare schema. Yet it omits units or valid ranges for friend_share and any expected format for agenda, so the semantics remain incomplete.

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 states a specific verb and resource: 'Create a referral link.' This is clear and unambiguous. However, it does not distinguish the tool from siblings such as nobitex_list_referral_links or nobitex_get_referral_status, so an agent must infer the boundary from the name alone.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or preconditions beyond the authentication note. The auth requirement is a prerequisite, but it does not explain when a referral link should be created or how it relates to the sibling referral tools.

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

Deploy Server

Other Tools