Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_update_deposit_address_title

Update the title of a deposit address by address ID. Set a new label or clear an existing title to keep saved addresses organized.

Instructions

Update the title of a deposit address.

Args: address_id: Address id from the list/generate endpoints. title: New title; empty/null clears it.

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": {
      "address_id": "<address_id>"
    },
    "name": "nobitex_update_deposit_address_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
address_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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. It does disclose one important behavioral trait — that an empty/null title clears the value — but says nothing about permissions, reversibility, or what the response contains for this mutation.

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?

Two short, front-loaded sentences with the action first and parameter notes after. The Args block is slightly redundant with the schema but adds real semantics rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter mutation with no output schema, the description covers the action, the id source, and the null-clearing behavior. Only permission/error context is missing, which is a minor gap at this complexity.

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

Parameters4/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, and it does: it explains that address_id comes from the list/generate endpoints and that title accepts empty/null to clear. Both parameters gain meaning beyond the bare schema 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: 'Update the title of a deposit address.' An agent can distinguish it from the generate/list siblings, though the description never names an alternative tool explicitly.

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?

Implies usage by pointing to where address_id comes from ('list/generate endpoints'), which is genuinely helpful context. However, it gives no explicit when-to-use/when-not guidance or prerequisites such as ownership or whitelist requirements.

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