Publish a post to Binance Square using YOUR Binance Square OpenAPI key (set in Integrations). Max 3 different $TICKER coin tags per post; write prices as plain numbers (no $). Daily limit: 100 posts.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Optional article title (max 200 chars) | |
| content | Yes | Post text (max 4000 chars) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the external posting action, credential requirement, formatting restrictions, and daily limit. However, it does not mention what the response contains, whether the post is immediately public, or what failure modes may occur (e.g., invalid key).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no fluff: the purpose comes first, followed by necessary constraints and limits. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool with no output schema or nested objects, the description is largely complete: it covers auth, content formatting, and rate limits. Minor gaps remain around expected response shape and potential errors, but they do not block correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameter basics are already documented. The description adds valuable content-level constraints beyond the schema: max 3 $TICKER tags and writing prices as plain numbers. This helps the agent construct valid post content.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (Publish a post), the target resource (Binance Square), and the required credential context (Binance Square OpenAPI key). It also includes specific constraints, making it distinct from the trading-oriented sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides clear context for when to use the tool: when publishing to Binance Square, with auth prerequisites and daily limits explained. It does not explicitly describe exclusions or alternatives, but no closely comparable sibling exists, so the implicit guidance is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools serve distinct purposes (hedging, funding, agents, market data), but several overlap heavily: get_basis_regime, get_basis_signal, get_basis_history, analyze_pair_liquidity, and get_perp_arbitrage all analyze exchange spreads/basis with blurred boundaries. Similarly, close_hedged_position vs close_position and hedge_status vs list_hedge_positions vs get_positions could cause misselection without careful reading.
The set predominantly follows a verb_noun pattern (get_*, open_*, close_*, set_*, list_*, place_*) which is predictable and readable. Minor deviations exist: agent_chat, agent_trigger, and square_post break the convention, and the hedge-specific tools mix status/list/adjust naming inconsistently.
35 tools is on the heavy side and pushes past the ideal scope for a single server. Many tools are data-retrieval variants (basis history/regime/signal/liquidity) that could be consolidated, and the breadth from news to square posts to agent management makes the surface feel sprawling rather than focused.
Core workflows (hedging, basis analysis, funding arbitrage, agent interaction, position management) are well covered, but there are noticeable gaps: there is no cancel_order tool despite get_open_orders and place_order existing, no order history or trade history, and no exchange-side position listing for real user positions. The server covers its niche but leaves some common trading dead ends.