Skip to main content
Glama
C0inFlips

binance-mcp-chainvector

by C0inFlips

BinanceWalletToggleBnbBurnOnSpotTradeAndMarginInterest

Enable or disable BNB burn for spot trading and margin interest, letting you pay fees with BNB and potentially save on transaction costs.

Instructions

Toggle BNB burn on spot trade and margin interest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recvWindowNoThe value cannot be greater than 60000
spotBNBBurnNo'true' or 'false' for spot trade
interestBNBBurnNo'true' or 'false' for margin interest
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. 'Toggle' implies a mutation, but there is no mention of side effects, required permissions, reversibility, or what the response contains. This is a significant gap for a state-changing wallet operation.

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 description is a single, front-loaded sentence with no redundant words. It immediately communicates the essential action and targets, making it highly efficient and easy to scan.

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?

Despite the simple parameter set, the lack of annotations or output schema means the description must explain return values, side effects, and usage context. It does none of these, leaving the agent without enough information to safely and correctly invoke the tool.

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?

The input schema covers all parameters with descriptions, so the baseline is 3. The description echoes the two context parameters (spot trade, margin interest) but adds no new syntactic or semantic details beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Toggle' and the resource 'BNB burn' with two specific contexts: spot trade and margin interest. It unambiguously distinguishes this tool from other Binance wallet tools like enable/disable fast withdraw switches or balance queries.

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 guidance is provided on when to use this tool versus alternatives, or any prerequisites or exclusions. The description only states what the tool does without contextualizing its use cases or edge cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/C0inFlips/binance-mcp-chainvector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server