koreanpulse

Search Korean industry news (16 sectors)

search_korean_industry_news

Read-onlyIdempotent

Korean industry news search across 16 sectors with on-demand English translation. Sources: 전자신문 (etnews) + 한국경제 (hankyung) + The Korea Herald (English-native) + 지디넷코리아 (zdnet). Free tier.

Use this tool when the user asks about: Korean industry trends, sector-specific news on Korean equities (Korean semiconductors / K-battery / K-shipbuilding / K-biotech / K-defense / Korean auto / EV charging / Korean AI / steel / petrochem / construction / fintech / gaming / e-commerce / telco / energy), recent corporate developments not yet captured in DART filings, English summaries of Korean industry coverage. Industry tags listed below — pass them in industries to filter.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	max articles (≤50).
`sources`	No	filter to source keys (etnews, hankyung, koreaherald, zdnet). None = all. koreaherald is English-native — its titles are returned as-is (no ko->en translation round-trip needed).
`translate`	No	server-side translates `title_en` for Korean-language sources. Cached aggressively. No-op for koreaherald (already English).
`industries`	No	filter to one or more industry tags. Available: semiconductor, shipbuilding, battery, biotech, defense, auto, ev_charging, ai, steel, petrochem, construction, fintech, gaming, ecommerce, telco, energy. An unrecognized tag is never silently dropped or errored — see Returns below.
`license_key`	No	required when license gate is enabled.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 12, 2026

changedInput schema / properties / industries / description

Previous value: -"filter to one or more industry tags. Available:\nsemiconductor, shipbuilding, battery, biotech, defense, auto,\nev_charging, ai, steel, petrochem, construction, fintech, gaming,\necommerce, telco, energy."New value: +"filter to one or more industry tags. Available:\nsemiconductor, shipbuilding, battery, biotech, defense, auto,\nev_charging, ai, steel, petrochem, construction, fintech, gaming,\necommerce, telco, energy. An unrecognized tag is never silently\ndropped or errored — see Returns below."

addedOutput schema / properties / result / anyOf

Added value: +[
+  {
+    "items": {
+      "description": "One Korean news article returned by `search_korean_industry_news`.",
+      "properties": {
+        "attribution": {
+          "description": "Required attribution string",
+          "type": "string"
+        },
+        "industries": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "published_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "relevance_score": {
+          "default": 0.5,
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        },
+        "snippet": {
+          "default": "",
+          "description": "~300-char plain-text excerpt from the RSS `description` field (HTML-unescaped, tags stripped, whitespace collapsed). No additional network fetch — derived from the same feed item as the title. Empty when the source's feed carries no description.",
+          "type": "string"
+        },
+        "source_key": {
+          "description": "Source id from sources.NEWS_SOURCES",
+          "type": "string"
+        },
+        "source_name": {
+          "description": "Korean source name for display",
+          "type": "string"
+        },
+        "summary_en": {
+          "description": "<= 200 word LLM summary in English. Always attributed.",
+          "type": "string"
+        },
+        "title_en": {
+          "description": "LLM-translated English title",
+          "type": "string"
+        },
+        "title_ko": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "title_ko",
+        "title_en",
+        "source_key",
+        "source_name",
+        "url",
+        "published_at",
+        "summary_en",
+        "attribution"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

removedOutput schema / properties / result / items

Removed value: -{
-  "description": "One Korean news article returned by `search_korean_industry_news`.",
-  "properties": {
-    "attribution": {
-      "description": "Required attribution string",
-      "type": "string"
-    },
-    "industries": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "published_at": {
-      "format": "date-time",
-      "type": "string"
-    },
-    "relevance_score": {
-      "default": 0.5,
-      "maximum": 1,
-      "minimum": 0,
-      "type": "number"
-    },
-    "source_key": {
-      "description": "Source id from sources.NEWS_SOURCES",
-      "type": "string"
-    },
-    "source_name": {
-      "description": "Korean source name for display",
-      "type": "string"
-    },
-    "summary_en": {
-      "description": "<= 200 word LLM summary in English. Always attributed.",
-      "type": "string"
-    },
-    "title_en": {
-      "description": "LLM-translated English title",
-      "type": "string"
-    },
-    "title_ko": {
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "title_ko",
-    "title_en",
-    "source_key",
-    "source_name",
-    "url",
-    "published_at",
-    "summary_en",
-    "attribution"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / result / type
```
Removed value: -"array"
```

Changed2 schema fields changedJul 7, 2026

changedInput schema / properties / sources / description

Previous value: -"filter to source keys (etnews, hankyung). None = all."New value: +"filter to source keys (etnews, hankyung, koreaherald, zdnet).\nNone = all. koreaherald is English-native — its titles are\nreturned as-is (no ko->en translation round-trip needed)."

changedInput schema / properties / translate / description

Previous value: -"server-side translates `title_en`. Cached aggressively."New value: +"server-side translates `title_en` for Korean-language\nsources. Cached aggressively. No-op for koreaherald (already\nEnglish)."

First observedMay 7, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context such as 'Free tier', the availability of on-demand English translation, and the specific sources, without contradicting any annotations. It does not describe caching or return behavior, but these are partly covered by the schema and output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently organized into two focused parts: a summary sentence and a 'Use this tool when' list. It is front-loaded with the core function, avoids unnecessary repetition, and every sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, usage scenarios, sources, and the free tier, while annotations and schema handle safety, parameters, and return values. The only minor gap is that the description references 'Returns below' but does not include that section itself (the schema covers it), and no explicit mention is made of rate limits or freshness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 5 parameters have rich descriptions in the schema, so the schema coverage is 100%. The description adds only marginal parameter-related context (e.g., mentioning the industries filter) and relies on the schema for full parameter semantics, matching the baseline of 3.

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 a specific action (search) on a specific resource (Korean industry news across 16 sectors) and names concrete sources. It distinguishes itself from sibling tools (which are about corporate codes, filings, and monitored entities) by its news-search focus and translation feature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists when to use the tool with concrete scenarios (e.g., 'Korean industry trends', 'recent corporate developments not yet captured in DART filings'). However, it does not explicitly state when not to use it or name alternative tools, so it stops short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All koreanpulse tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.