Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_add_bank_account

Add a bank account (IBAN/SHABA) to a Nobitex profile to link withdrawal details, with an optional account number.

Instructions

Add a bank account (IBAN/SHABA) to the user's profile.

Args: shaba: SHABA/IBAN number. number: Optional account number.

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": {
      "shaba": "<shaba>"
    },
    "name": "nobitex_add_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
shabaYes
numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.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 burden and does little: it never says whether the account must be verified/confirmed afterward, whether existing accounts are affected, what permissions or authentication are needed, or what the call returns. For a profile-mutating financial operation this is a significant gap.

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?

Front-loaded single-sentence purpose followed by a compact Args block; nothing is padded. The Args section is somewhat redundant for parameters already named in the schema but is short enough not to hurt.

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 two-parameter mutation tool with no annotations and no output schema, the definition covers the bare mechanics but omits verification flow, idempotency/duplicate handling, and error or success behavior — all of which an agent would need to set expectations.

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 does supply the only documentation for both parameters, including that the value is a SHABA/IBAN format and that 'number' is optional. It adds no format example, validation constraints, or note on whether 'number' is required for certain bank types.

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 account (IBAN/SHABA)') and scopes it to the user's profile, which distinguishes it from the sibling nobitex_add_bank_card by instrument type. It stops short of explicitly naming the card/address-book siblings as alternatives.

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 name and phrasing imply the obvious create-a-bank-account scenario, but there is no explicit when-to-use, no mention of alternatives (add card vs add bank account), and no stated prerequisites such as whitelist or verification status.

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