get_korea_tourism
Get Korean tourism places and attractions in English.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | ||
| lang | No | ||
| type | No |
kdata-gate
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It only states 'Get' implying read-only but does not mention any behavioral traits such as rate limits, authentication, or response characteristics.
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 short sentence, which is concise but lacks detail. It is not wasteful, but could be expanded with parameter hints without becoming verbose.
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 3 undocumented parameters, no output schema, and no annotations, the description is highly incomplete. An agent cannot determine valid parameter values, defaults, or the structure of results.
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 three parameters (area, lang, type) with no descriptions. Schema description coverage is 0%, and the tool description provides no additional meaning or examples for these parameters, leaving the agent without guidance on how to populate them.
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 verb 'Get', the resource 'Korean tourism places and attractions', and the scope 'in English'. This distinguishes it from sibling tools like get_korea_weather or get_korean_stock_prices.
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 usage guidance is provided. The description does not indicate when to use this tool versus alternative tools for Korean data, nor are there any prerequisites or exclusions mentioned.
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.