Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_withdrawal

Fetch one withdrawal's details by ID to confirm its status, amount, and destination on Nobitex.

Instructions

Get details of one withdrawal by id.

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": {
      "withdraw_id": "<withdraw_id>"
    },
    "name": "nobitex_get_withdrawal"
  }
}

Input Schema

NameRequiredDescriptionDefault
withdraw_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'Get' implies a read-only operation, but nothing is said about authentication requirements, ownership scoping, what happens for unknown or foreign IDs, or error behavior. For a financial-account read tool this leaves meaningful gaps.

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?

A single short sentence is front-loaded with the verb and resource, with no filler. It is terse to the point of under-specification, 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, so the description should say what 'details' includes (status, amount, currency, timestamps), yet it does not. Combined with a single undocumented parameter and no annotations, the definition is too thin for an agent to call it confidently.

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

Parameters2/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; 'by id' only weakly ties withdraw_id to the lookup. It does not say the id is an integer, where it comes from (for example a prior request/list response), or whether it refers to a Rial or crypto withdrawal.

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 ('Get') and resource ('details of one withdrawal') scoped to a single record, which distinguishes it from list-style siblings. It does not explicitly differentiate itself from nobitex_get_rial_withdrawal, which is a close relative, so it falls short of a 5.

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 or when-not-to-use guidance is given; there is no mention of prerequisites, of which withdrawal types are covered, or of when a sibling such as nobitex_get_rial_withdrawal is the better call. The agent must infer usage entirely from the name.

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