binance_get_trading_scheduleJadwal sesi trading untuk underlying assets (US, Korea, Hong Kong, China, commodities). Sangat relevan untuk TradFi perpetual.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations bieten schon readOnlyAngle und openWorldSnap. Die Beschreibung ergänzt Informationsumfang: Abdeckung bestimmter Märkte sowie Relevanz für TradFi-Perpetuals. Sie fügt keine Details zu Zeitform, Zeitzone oder Ausgabeformat hinzu, was für den vollen Kontext abverlangt wäre.
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?
Zwei Sätze ohne redundante Information. Der Hauptgegenstand ist vorgelagert, die Relevanz-Aussage ist wie zusätzliche Semantik plaziert ohne Ballast.
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?
Für ein parameterloses, einfaches Get-Teile ist die Beschreibung ausreichend vollständig: Sie nennt zugrunde liegende Asset-Märkte und den Anwendungsfall. Es fehlt keine Parameter- oder Ausgabe symbol nötig; nur ein konkretes Format der Rückgabe wäre noch eventuell erwünscht.
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?
Das Tool hat keine Parameter, damit die Schema-Abdeckung ist 100 %. Die Beschreibung muss daher keinen Parameter-Kontext liefern. Die notwendige Abstraktion ist erreicht.
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?
Beschreibung legt Gegenstand klar fest: Handelszeiten/Handelszeiten für Basiswerte aus US, Korea, Hongkong, China und Rohstoffe. Der Verwendungszweck wird deutlich vom Toolnamen unterschieden, auch wenn kein explizites Listenausführungsverb vorhanden ist.
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?
Die Angabe 'Sangat relevan untuk TradFi perpetual' liefert expliziten Kontext, wann dieses Tool nützlich ist. Alternativen werden nicht benannt/ausgeschlossen, aber für ein parameterloses Planungs-Symbol ist keine förmliche Abgrenzung nötig.
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.
Most tools map to a distinct Binance metric or analytic concept, and descriptions explicitly contrast near-neighbors (spot vs futures, snapshot vs delta, 'BEDA dari...' notes). A few pairs could still be confused—`binance_get_basis` vs `binance_get_basis_history` and `binance_get_agg_trades` vs `binance_get_recent_trades`—but their purpose differences are explained well enough for careful agents.
The dominant pattern is `binance_<verb>_<object>` in snake_case, with consistent complementary pairs like `get_*` and `get_*_history`. There are minor style breaks: `orderbook` vs `order_book`, the `whalescope_*` prefix, and `whalescope_full_pipeline` which lacks a verb, but the overall structure is readable and predictable.
56 tools cross the explicit '50+ tools' extreme threshold. Although the Binance Futures domain is broad, many tools are single-endpoint or single-metric wrappers—multiple klines variants, order book variants, and ticker variants—that could be consolidated into parameterized composite tools. The surface is far too large for most agents to navigate efficiently.
The public market-data and analytics surface is remarkably complete: klines, funding, open interest, long/short ratios, top-trader data, liquidations, basis, order book behavior, regime detection, and full pipeline scoring are all covered. The main gaps are documented limitations such as unavailable liquidation-by-price data and non-public account/execution tooling, but agents can work around them without dead ends.