Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_set_referrer

Registers a referrer code for a Nobitex user via a required user token; use it when API-key authentication is not accepted for this endpoint.

Instructions

Register a referrer code for the user.

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

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": {
      "referrer_code": "<referrer_code>"
    },
    "name": "nobitex_set_referrer"
  }
}

Input Schema

NameRequiredDescriptionDefault
referrer_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It usefully discloses the token-based auth requirement, which is genuine behavioral context beyond the schema. It does not disclose whether an existing referrer is overwritten, whether the call is idempotent, or what a failure looks like, leaving significant gaps for a state-mutating endpoint.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and followed by the auth constraint. Every sentence carries information an agent needs, with no redundancy or filler.

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 single-parameter mutation with no annotations and no output schema, the description covers the action and the auth model but omits overwrite semantics, error behavior, and the expected code format. It is adequate to attempt a call but not complete enough to predict its effects.

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%, and the description only restates the parameter's meaning via the tool name ('referrer code'). It does not indicate whether the value is a numeric user ID, a username, or an alphanumeric code, nor any format or validation constraints, so it adds essentially no meaning beyond the schema.

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 and resource: 'Register a referrer code for the user.' This clearly distinguishes it from read-only or link-creation siblings in the referral family. It stops short of explicitly naming how it differs from a tool like nobitex_create_referral_link, so it is clear but not fully differentiated.

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 description supplies a crucial prerequisite — a user token is required and API-key auth will not work — which tells the agent when this tool is callable. However, it offers no guidance on when to choose this over sibling referral or account-setting tools, nor any exclusions.

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