binance-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation3/5
There is notable overlap among get_funding_wallet, get_spot_account, get_account_overview, and get_portfolio_snapshot, all of which return balance-related information. While descriptions differentiate them, the boundaries are not immediately clear, and get_account_overview vs get_portfolio_snapshot could easily be confused.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: get_ for queries and accept_ for the conversion action. The naming is predictable and uniform across the entire set.
Tool Count5/5
With 10 tools, the server is well-scoped for its focus on account/portfolio reads and Convert operations. Each tool serves a distinct purpose without unnecessary bloat.
Completeness3/5
The server covers account balances, Convert quotes/execution/status/history, and basic market data, but it lacks core Binance trading features such as placing/canceling spot orders or retrieving order history. This leaves significant gaps if a broader Binance workflow is expected.
Average 3.5/5 across 10 of 10 tools scored. Lowest: 2.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 12 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It implies a read operation via 'Get' but does not explicitly state read-only safety, permission requirements, rate limits, or any side effects. The description only restates the function without adding contextual behavioral traits.
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, focused sentence with no redundant information. It is concise and front-loaded, effectively communicating the tool's purpose without unnecessary filler.
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 clarify the return format or structure. It does not explain what the snapshot includes (e.g., spot vs. funding balances), how it aggregates data, or how it differs from sibling tools. The description is too terse to be fully self-contained for an agent unfamiliar with the context.
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?
Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description's mention of 'live valuation' adds minimal contextual flavor around valuationQuoteAsset, but it does not materially enhance parameter understanding beyond the schema's provided descriptions.
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 uses a specific verb 'Get' and resource 'balances and a live valuation snapshot', clearly stating the tool's core function. However, it does not distinguish itself from sibling tools like get_spot_account or get_account_overview, which also retrieve balances, so it lacks sibling differentiation.
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. The phrase 'in one call' hints at a convenience advantage, but there is no explicit mention of when it should be preferred over sibling tools or any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavior. It does not state that this is a read-only operation, nor does it mention authentication requirements, potential errors, or response structure beyond 'balances and account flags.' Given it's a get, some traits are implied, but it lacks explicit transparency.
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?
Single sentence, front-loaded with the verb 'Get', and includes the most relevant scope. No redundant information.
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 simple one-param read tool, the description is minimally sufficient. It identifies the resource and output categories, but given the presence of similar sibling tools and no output schema, additional context on exact return format or use-case differentiators would improve completeness. However, complexity is low.
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?
Schema description coverage is 100%, with the parameter omitZeroBalances explained in the schema. The tool description adds no additional parameter semantics, only mentioning the general content. Consequently, baseline 3 is appropriate as the schema already handles it.
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?
Clearly states 'Get the current Binance spot account, including balances and account flags.' This is a specific verb and resource ('spot account') with output components. However, it doesn't explicitly distinguish from sibling tools like get_account_overview or get_portfolio_snapshot, which may also deal with account data.
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?
The description gives no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, preferred use cases, or exclusions. Sibling tools such as get_account_overview and get_portfolio_snapshot exist, but no comparison is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states that it 'gets' balances, but does not mention authentication requirements, return format, how the optional asset filter behaves, or any edge cases like empty balances. For a read tool, this is minimal and lacks helpful context.
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, concise sentence with no redundant or extraneous information. It is efficient and front-loaded with the essential verb and resource.
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?
The tool is relatively simple with only two optional parameters, but the description omits the output structure entirely and there is no output schema to compensate. It states 'balances' without clarifying whether it returns a list, an object keyed by asset, or additional details like locked vs available balances. This leaves some ambiguity for the agent.
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 provides full descriptions for both parameters (asset and needBtcValuation), with 100% coverage. The tool description does not add any parameter-level meaning, so the baseline of 3 applies here.
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 uses the specific verb 'Get' and clearly identifies the resource as 'Binance funding wallet balances', distinguishing it from sibling tools like get_spot_account or get_portfolio_snapshot. The scope is unambiguous and directly reflects the tool's function.
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?
The description provides no guidance on when to use this tool versus alternatives such as get_spot_account or get_account_overview. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer applicability from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description is the only source of behavioral context. It does not disclose read-only nature, response structure, pagination, or any side effects. The phrase 'overview' hints at a high-level view but adds little beyond the purpose statement.
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 that directly communicates the core function. It is concise and free of redundancy, achieving high clarity with minimal words.
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 and the description says nothing about return format, data shape, or how this differs from get_portfolio_snapshot. Given the lack of annotations and the presence of sibling tools that may overlap, the description is incomplete for safe and accurate tool selection.
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?
Schemas already provide 100% coverage for all three parameters with descriptions. The tool description does not add any parameter-specific meaning, so the baseline of 3 applies.
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 'combined overview' of spot and funding wallet balances, which directly distinguishes it from sibling tools get_spot_account and get_funding_wallet. The verb 'get' and specific resource markers make the purpose unambiguous.
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?
The description implies a use case (when both balance types are needed) but does not explicitly state when to use this tool versus the alternatives. It lacks direct exclusions or mentions of alternatives, so the agent is left to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the action but does not disclose behavioral details such as read-only nature, what happens if neither or both identifiers are provided, required permissions, or potential error cases. This is a significant gap for a tool with two optional parameters.
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 12-word sentence that is front-loaded with the verb and resource. It contains no filler, making it extremely concise and well-structured.
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?
The tool is simple with two optional parameters and no output schema. The description does not clarify whether at least one identifier is required, nor does it describe the return format or error behavior. However, given the simplicity, the basic purpose is clear, but completeness is limited.
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 schema already provides descriptions for both orderId and quoteId, achieving 100% coverage. The description's mention of 'by orderId or quoteId' adds a minor note about interchangeability but does not add substantial meaning beyond the schema.
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 uses the specific verb 'Check' and identifies the exact resource: 'status of a Binance Convert order' with two lookup identifiers. This clearly distinguishes it from sibling tools like get_convert_quote (get a quote) and get_convert_trade_history (list trade history).
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?
The description implies usage for checking the status of a specific convert order after placing it, but does not explicitly mention when to choose this over alternatives such as get_convert_trade_history or accept_convert_quote. No exclusions or alternative mentions are present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The phrase 'live conversion' discloses that this performs a real, potentially irreversible trade action, which is useful since no annotations are provided. However, it does not mention risks, required funds, or whether the quote is consumed, leaving some behavioral aspects undisclosed.
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 only two sentences, with no redundant information. Every word contributes to conveying the action and its live nature, making it highly concise.
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 single-parameter tool with no output schema, the description is largely sufficient—it states what it does and the schema documents the parameter. However, it does not mention what the tool returns or how to follow up, though sibling tools like get_convert_order_status provide some context.
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 schema covers 100% of the parameter description, including 'The quote ID returned by get_convert_quote.' The tool description adds no additional parameter information, so the baseline of 3 is appropriate.
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 tool's purpose: 'Execute a Binance Convert quote' with a specific verb and resource. It distinguishes itself from sibling tools like get_convert_quote by implying the action of executing rather than fetching.
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?
The description implies that the tool is used when a quote is ready to be executed, but it does not explicitly mention prerequisites, alternatives, or exclusions. The schema clarifies that quoteId comes from get_convert_quote, but this is not in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description is minimal. It states what the tool returns (bid and ask) but does not disclose any additional behavioral traits such as rate limits, response structure for multiple symbols, or whether the data is a snapshot.
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 sentence that directly states the tool's function. It is concise and front-loaded with the key action and resource.
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?
Given the tool's simplicity (one parameter, read-only, no output schema), the description is sufficient but not exhaustive. It would benefit from specifying return format when multiple symbols are requested, but it is adequate for basic invocation.
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 schema already describes the 'symbols' parameter with examples, achieving 100% coverage. The description's mention of 'one or more Binance spot symbols' adds no additional semantic value beyond the parameter description.
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 uses a specific verb 'Get' and resource 'current best bid and ask' for 'Binance spot symbols', which clearly distinguishes it from sibling tools like get_last_prices that return different market data.
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?
The description implies the tool should be used when the agent needs the best bid and ask, but it does not explicitly state when not to use it or mention alternative tools like get_last_prices for last price data.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the transparency burden. It does disclose the key behavioral trait that the tool is non-executing, which implies read-only behavior. However, it does not mention other relevant details such as authentication requirements, whether the quote guarantees a price, or how the quote is delivered (e.g., in response vs. a quote ID). The disclosure is useful but incomplete.
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 two short sentences that are direct and front-loaded. The first sentence states the primary purpose, and the second clarifies a critical caveat. There is no waste, and every word contributes value.
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?
The description is minimal for a tool with 6 parameters, no output schema, and no annotations. It does not explain what the quote response will contain (e.g., total, quoteId, expiry), how to interpret the response, or the workflow step of subsequently accepting the quote. Given the absence of an output schema, the description should provide more context about return values and the typical usage flow.
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 schema description coverage is 100%, with each parameter having a meaningful description (e.g., 'Source asset', 'Exact destination amount'). The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.
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 'Request' and the specific resource 'a Binance Convert quote', and immediately clarifies it does not execute the conversion, distinguishing it from the sibling tool accept_convert_quote. This is a specific, non-tautological purpose.
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?
The description implies clear usage context: to obtain a quote without executing. While it does not explicitly name alternatives, the phrase 'does not execute the conversion' strongly suggests using accept_convert_quote for execution. The sibling list reinforces this separation, but explicit guidance would be stronger.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the transparency burden. It accurately describes the read-only nature by stating it 'gets' prices, and it adds useful context like 'spot symbols' and 'latest'. However, it does not disclose return format, error handling, or rate limits, which are relevant for a tool with no annotations.
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 sentence with no filler. Every word adds value, and the core verb and object are front-loaded. It is concise without losing necessary detail.
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?
Given the tool's low complexity (one parameter, no output schema, no annotations), the description is largely sufficient. It clarifies the resource and scope. It could optionally mention the return shape (e.g., a mapping of symbols to prices), but for a tool named get_last_prices this is easily inferred, so a slightly above-minimum score is warranted.
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 schema covers 100% of the parameter description, including examples like 'BTCUSDT or ETHUSDT'. The tool description adds the modifier 'spot', but the schema already provides sufficient semantic detail. Baseline score of 3 is appropriate given high schema coverage.
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 action ('Get'), the target resource ('latest Binance last-traded prices'), and the scope ('one or more spot symbols'). It distinguishes itself from siblings like get_book_ticker by explicitly focusing on last-traded prices rather than order book data.
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?
The description implies usage when a user needs the latest last-traded price for spot symbols, but it does not explicitly mention alternatives or when not to use it. Sibling tools such as get_book_ticker exist, but no guidance is provided for choosing between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It discloses the 30-day limit, which is a meaningful constraint not in the schema, and the verb 'Get' implies a read-only operation. However, it does not mention pagination behavior, ordering, rate limits, or whether the result includes only completed trades, leaving some behavioral gaps.
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, concise sentence that conveys the core function and a key restriction with no redundant words. It is front-loaded and easily parsed, earning the maximum score for efficiency.
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?
Given the tool's simplicity (3 parameters, no nested objects) and the absence of an output schema, the description provides sufficient context: it names the resource and the time constraint. It does not explain the return format or pagination, but for a read-only history tool, the essential information is present. A slightly richer description of expected output or edge cases would push it to a 5.
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?
The schema already provides descriptions for all parameters (100% coverage), including startTime, endTime, and limit. The description adds value by clarifying that the startTime–endTime window must be 30 days or less, which is a constraint not present in the schema. This gives the agent better understanding of how to set parameters correctly.
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 tool's function as retrieving Binance Convert trade history, and specifies a key constraint ('30-day window or less'). This distinguishes it from sibling tools like get_convert_order_status (status retrieval) and get_convert_quote (quote generation), making the purpose unambiguous.
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?
The description implies usage context by specifying the time window limitation, but it does not explicitly state when to use this tool over alternatives or provide exclusion criteria. It lacks clear guidance on scenarios where get_convert_order_status would be more appropriate, so the usage guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![Binance-MCP MCP server](https://glama.ai/mcp/servers/mujeeb8/Binance-MCP/badges/card.svg)](https://glama.ai/mcp/servers/mujeeb8/Binance-MCP)

Score Badge

Copy to your README.md:

[![Binance-MCP MCP server](https://glama.ai/mcp/servers/mujeeb8/Binance-MCP/badges/score.svg)](https://glama.ai/mcp/servers/mujeeb8/Binance-MCP)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/mujeeb8/Binance-MCP'

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