Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_add_bank_card

Add a bank card to a Nobitex user profile by supplying the card number and optional bank name, enabling fiat withdrawals and account payout setup.

Instructions

Add a bank card to the user's profile.

Args: number: Card number. bank: Bank name; defaults to "سایر" on the server.

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": {
      "number": "<number>"
    },
    "name": "nobitex_add_bank_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNo
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden for a mutation tool. It does not say what happens on a duplicate card, whether the card is immediately usable or needs verification, whether the operation requires an authenticated session, or what the response looks like. The only behavioral hint is the server-side default for the bank field.

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 one-line purpose statement is front-loaded and the argument list is compact with no filler. Minor deduction because the raw docstring "Args:" block is carried over verbatim rather than written as prose, but nothing is wasted.

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?

There is no output schema and no annotations, so the description is the only source of behavioral information, and it omits the return value, duplicate-handling, verification requirements, and error conditions. For a write operation on a financial profile it leaves too much for the agent to guess.

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 coverage is 0%, so the description must compensate, and it does partially: it labels both parameters and clarifies that the server substitutes "سایر" when bank is omitted, which the schema (default: null) obscures. However, it adds no format constraints for the card number (digits, spaces, length) and gives no example bank values.

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?

States a specific verb and resource: "Add a bank card to the user's profile." An agent can tell it apart from nobitex_delete_bank_card by the verb, but the description never distinguishes it from nobitex_add_bank_account, which is a plausibly confusable sibling.

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?

No when-to-use guidance, no prerequisites (e.g. whether the card must later be confirmed, whether a whitelist or KYC is required), and no mention of alternatives such as adding a bank account instead. The agent must infer everything from the sibling names.

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