Get all available trading symbols on Korean exchanges. Returns symbols available on Upbit, Bithumb, and those common to both. Use this to check which symbols you can query before calling other tools.
š° Price: FREE (no x402 payment required)
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint and openWorldHint, establishing the tool as safe and external. The description adds meaningful context beyond annotations by specifying the exact exchanges covered (Upbit, Bithumb, common) and stating the tool is free of charge, which is useful for agents evaluating cost.
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?
The description is extremely concise, with two clear sentences and a price note. It front-loads the action ('Get all available trading symbols...'), and every sentence contributes value without redundancy.
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?
Given the tool's simplicity (zero parameters) and the presence of an output schema, the description sufficiently covers purpose, usage context, and return scope. It also includes the pricing detail, which is relevant for other tools in the family.
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?
The tool has zero parameters, and the schema coverage is 100%, so the description carries no parameter burden. The baseline for no parameters is 4, and the description appropriately adds no unnecessary parameter details.
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 tool's purpose: retrieving available trading symbols from Korean exchanges, specifically naming Upbit and Bithumb. It distinguishes itself from sibling get_* tools by focusing on symbol availability rather than prices, alerts, or news.
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?
The description explicitly instructs users to use this tool before calling other tools to check which symbols can be queried, providing clear usage context. However, it does not mention when not to use it or name alternatives, but for this generic symbol-listing tool such exclusions are not critical.
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 have distinct purposes (prices, alerts, news, health), but several overlap: get_kimchi_premium vs get_arbitrage_scanner both cover premium data, and get_kr_sentiment, get_market_read, and get_global_vs_korea_divergence_deep all provide AI analysis with different scopes, which could confuse an agent.
All tools follow a consistent get_<descriptive_noun> pattern in snake_case, with check_health as the only deviation, which is a conventional health-check exception. The naming is highly predictable.
With 17 tools, the server is on the heavy side per the calibration (16-25 feels heavy). While the domain is broad and each tool has a role, the existence of paired summary/deep variants adds redundancy that could be consolidated.
The tool set covers a comprehensive Korean crypto intelligence surface: prices, premiums, arbitrage, alerts, sentiment, market analysis, FX, news, and health. Minor gaps like a general Korean crypto news tool or historical data are not critical but prevent a perfect score.