get_korean_stock_flows
Get Korean investor flow, program trading, short, and lending data.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | ||
| ticker | No | ||
| date_to | No | ||
| investor | No | ||
| date_from | No |
kdata-gate
TDQS
C2.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully disclose behavior. It only states it 'gets' data but does not mention read-only nature, rate limits, authentication needs, or pagination. The minimal description is insufficient for safe invocation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 12 words, which is concise, but it lacks structure and important details. It is front-loaded but under-specified.
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?
With 5 parameters, no output schema, and no annotations, the description is critically incomplete. It fails to explain the returned data, filtering behavior, or any constraints, making it inadequate for reliable tool invocation.
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?
The input schema has 5 parameters with 0% documentation coverage. The description adds no information about valid values, formats, or semantics (e.g., market codes, date format, investor types). The agent must guess parameter usage.
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 clearly states the verb 'Get' and lists specific data types (investor flow, program trading, short, lending data). However, it does not differentiate from sibling tools like get_korean_stock_prices or get_korean_stock_fundamentals, which are distinct in purpose.
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. There is no mention of context, prerequisites, or exclusions, leaving the agent without decision support.
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.