Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_confirm_address_book_item

Confirms a pending address-book entry by submitting its ID and the OTP from the address-book request, completing two-step verification.

Instructions

Confirm an address-book item (step 2 of 2).

Args: id: address_book_item_id from the create step. otp_code: OTP obtained from /v2/otp/request with usage=address_book.

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": {
      "id": "<id>",
      "otp_code": "<otp_code>"
    },
    "name": "nobitex_confirm_address_book_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
otp_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does supply real context: the OTP must be pre-obtained from /v2/otp/request with usage=address_book, and the id comes from a prior create. It does not say what confirmation changes, whether it is reversible, what happens on an invalid or expired OTP, or whether it can be re-issued — significant gaps for a confirmation mutation.

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?

Front-loaded purpose line followed by a two-entry args block, with no filler. Every sentence is actionable for an agent assembling the call.

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 confirmation tool with no output schema and no annotations, the definition covers how to obtain both inputs but leaves the outcome underspecified. An agent knows how to call it but not what it gets back or how failures manifest.

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 document both parameters, and it does: id is the address_book_item_id from the create step, and otp_code is the OTP from /v2/otp/request with usage=address_book. That provenance is more useful than a plain type restatement, though it omits format details like OTP length or expiry.

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 names a specific verb and resource ('Confirm an address-book item') and adds the workflow position '(step 2 of 2)', which separates it from the create/add siblings in the address-book family. It stops short of naming the create sibling explicitly, but 'the create step' makes the pairing unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: this is the second half of a two-step flow, invoked after creating an item, and the id must come from that create step. No explicit when-not guidance or failure/retry conditions are given, so it is not fully exhaustive.

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