get_korean_stock_overview
Get Korean stock market overview rows.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | ||
| sector | No | ||
| ticker | No |
kdata-gate
TDQS
C2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It only states 'Get' without disclosing whether the operation is read-only, destructive, or any side effects. No mention of authentication, rate limits, or return behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (6 words) but at the expense of informativeness. It does not provide enough detail to be useful, making it under-specified rather than efficiently concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given three optional parameters and no output schema, the description is incomplete. It does not explain what the tool returns, how parameters filter results, or any example usage. The description is insufficient for effective agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no meaning to the three parameters (market, sector, ticker). It fails to explain what values are valid or how they affect the results.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Get Korean stock market overview rows' with a clear verb and resource, but it is vague and does not differentiate from sibling tools like get_korean_stock_prices or get_korean_stock_fundamentals. It lacks specificity about what 'overview rows' entails.
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 such as other Korean stock tools. There are no when-not scenarios or alternative suggestions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.9/5.0
Disambiguation4/5
Most tools have distinct purposes, but create_buy_ship_cart_order and create_direct_buy_ship_order are nearly identical, causing potential confusion. Additionally, build_buyer_discovery_queue and build_cash_sprint_packet overlap in targeting buyer segments.
Naming Consistency5/5
All tools follow a clear verb_noun pattern (build_, get_, create_, search_) with consistent snake_case, making it easy to infer functionality from the name.
Tool Count3/5
With 26 tools covering diverse domains (stock market, real estate, tourism, sourcing, etc.), the scope feels broad and somewhat bloated. A more focused set would improve coherence.
Completeness3/5
The tool set covers many aspects of Korea data and seller workflows, but notable gaps exist: no tools for actual listing posting, sending communications, or completing transactions, as many build_ tools explicitly exclude those steps.