Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_settlement_settings

Retrieves current custodial settlement settings, including whether auto-settlement is enabled, settlement frequency, and next scheduled trigger time.

Instructions

Get current settlement settings for custodial solution.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Shows automatic settlement configuration and schedule.

Response includes:

  • settlementActive: Whether auto-settlement is enabled

  • frequencyInHours: Settlement frequency (e.g., 24 hours)

  • nextTriggerTime: Timestamp of next scheduled settlement

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": {
      "rail": "<rail>"
    },
    "name": "binance_us_cust_settlement_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full disclosure burden; it does state the auth requirement for the custodial API key and that the operation surfaces the auto-settlement schedule. It enumerates the returned fields (settlementActive, frequencyInHours, nextTriggerTime), which materially informs an agent about the payload. Rate limits and failure modes are not covered, keeping it below a 5.

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?

The purpose is front-loaded in the first line, followed by a clearly marked prerequisite and a compact bulleted list of return fields. Every element earns its place, and the response bullets are justified because there is no output schema.

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 single-parameter read tool with no output schema and no annotations, the definition covers purpose, auth prerequisite, and return shape, which is nearly everything an agent needs to invoke it. Only error/edge behavior is absent.

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?

With one parameter at 100% schema description coverage, the schema already documents "rail" including the uppercase custodial partner examples. The description adds no further meaning to that argument, so the baseline of 3 applies.

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?

"Get current settlement settings for custodial solution" gives a specific verb (get) and resource (settlement settings), and "current" plus "automatic settlement configuration and schedule" distinguishes it from the settlement_history siblings. It does not name any alternative tool explicitly, so sibling differentiation is implied rather than stated.

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 infers it should call this to read the current settlement configuration rather than a history listing. The definition does supply a real prerequisite ("REQUIRES CUSTODIAL SOLUTION API KEY"), but offers no explicit when-to-use vs. when-not or named alternatives.

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