get_korea_fx_macro
Get Korea FX rates and macro indicators.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| period | No | ||
| indicator | No |
kdata-gate
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description does not disclose any behavioral aspects such as data freshness, rate limits, authentication needs, or whether the tool is reversible. It merely states the action without additional transparency.
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 extremely concise (one sentence), but it sacrifices necessary detail. While there is no waste, it is under-specified for effective use.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of annotations, output schema, and parameter explanations, the description is insufficient for an agent to understand the tool's full capability and constraints. It lacks completeness for a tool with two unexplained parameters.
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?
With 0% schema description coverage and no parameter details in the description, the meaning of 'period' and 'indicator' is entirely ambiguous. The description adds no semantic value beyond the schema's structure.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves Korea FX rates and macro indicators, specifying both the domain (Korea) and the data type. This distinguishes it from sibling tools like get_korean_stock_prices or get_korea_real_estate.
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, nor are there any prerequisites or contextual cues. The description simply states what it does without any usage context.
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.