Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_validate_address_network

Validate a destination wallet address and optional tag/memo for a specified blockchain network to help confirm withdrawal details before sending funds.

Instructions

Validate a destination address (and optional tag) for a network.

Args: network: Network name, e.g. "BSC". address: Destination wallet address. tag: Optional tag/memo.

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": {
      "network": "<network>",
      "address": "<address>"
    },
    "name": "nobitex_validate_address_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
addressYes
networkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose a genuine behavioral fact: a user token is required and API-key auth is rejected for this endpoint. It does not say what 'validate' checks (format only vs. network/address compatibility), whether failure is an exception or a false result, or whether the call has any side effects.

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 purpose sentence, then a compact Args block and one auth note; nothing is padded. The Args block partially restates schema titles, but the added examples justify its presence.

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 three-parameter tool with no annotations and no output schema, the definition should cover return semantics and valid network values; it covers auth and per-parameter meaning but leaves the agent guessing about the result and the accepted network set.

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 Args block does real work: it gives a concrete network example ('BSC') and clarifies that tag is a memo. However, it omits the most important semantics — which network values are legal (no enum in the schema) and the fact that address format is network-dependent.

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 ('Validate a destination address ... for a network') with the optional tag scope called out. It is clearly distinguishable from sibling mutation tools like nobitex_generate_deposit_address or nobitex_add_address_book, though it does not explicitly name a sibling to contrast with.

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?

Usage is only implied: an agent can infer this belongs before a withdrawal or address-book write, but the description never says when to call it, whether it is a prerequisite for other tools, or what to do on failure. The one explicit routing statement is about auth (user token required), not about tool selection.

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