Skip to main content
Glama

koreanpulse

by io.github.whdrnr2583-cmd

Resolve KRX 6-digit ticker to DART corp entry

resolve_stock_code
Read-onlyIdempotent

KRX 6-digit ticker → DART corp entry resolver. Free tier.

Use this tool when the user provides a 6-digit Korean stock code (e.g. 005930 for Samsung Electronics, 000660 for SK hynix, 035420 for NAVER, 035720 for Kakao, 005380 for Hyundai Motor) and you need the company name + corp_code for downstream filings or industry-news lookups.

When the code is unresolved but looks like a Korean preferred-stock ticker (6 digits, non-zero last digit, e.g. 005935 for 삼성전자우), the response carries an additive related_common_stock hint pointing at the common-stock entry — the corp registry only maps common stock, so no preferred-stock corp_code is fabricated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stock_codeYes
license_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "description": "One entry from DART's corp index.",
-    "properties": {
-      "corp_code": {
-        "type": "string"
-      },
-      "corp_name": {
-        "type": "string"
-      },
-      "modify_date": {
-        "type": "string"
-      },
-      "stock_code": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "corp_code",
-      "corp_name",
-      "stock_code",
-      "modify_date"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "One entry from DART's corp index.",
+    "properties": {
+      "corp_code": {
+        "type": "string"
+      },
+      "corp_name": {
+        "type": "string"
+      },
+      "modify_date": {
+        "type": "string"
+      },
+      "stock_code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "corp_code",
+      "corp_name",
+      "stock_code",
+      "modify_date"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the free tier, the common-stock-only mapping limitation, and the unresolved preferred-stock behavior with `related_common_stock` hint. It also states that no preferred-stock corp_code is fabricated, which is valuable non-obvious behavior.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and free-tier note, followed by clear usage and an edge-case explanation. It is somewhat long with many examples, but every sentence contributes useful information without fluff.

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?

With an output schema available, the description does not need to enumerate return fields. It provides the main purpose, usage trigger, and a key edge case, making it sufficiently complete for an agent; only minor gaps remain around license_key and rate-limit details.

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

Parameters4/5

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

The schema only has typed parameters with no descriptions, so the description's examples (005930, 000660, 035420) and format guidance ('6-digit Korean stock code') add meaning to `stock_code`. However, the optional `license_key` parameter is not explained in the description.

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 opens with a clear mapping statement ('KRX 6-digit ticker → DART corp entry resolver') and provides concrete examples (005930, 000660). This directly states the tool's function and distinguishes it from sibling lookup/search tools by identifying the precise input and output.

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?

It explicitly says 'Use this tool when the user provides a 6-digit Korean stock code...' and frames the need as getting corp_code for downstream filings or news lookups. It lacks explicit exclusions or alternative tool names, but the context is clear enough for an agent to select it.

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

All koreanpulse toolsInspect
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.

TDQS

A4.4/5.0
Disambiguation4/5

Tools are mostly distinct, but lookup_corp_code and resolve_stock_code both resolve to corp codes (by name vs ticker), and track_korean_filings overlaps with the two monitor tools on raw 5% filings. However, descriptions are explicit about the differences, especially the paid monitors' classification role, so an agent can disambiguate with careful reading.

Naming Consistency5/5

All tools follow verb_noun snake_case pattern (lookup_corp_code, monitor_activist_investors, monitor_foreign_holders, resolve_stock_code, search_korean_industry_news, track_korean_filings). The only exception is koreanpulse_about, which uses a server-namespace prefix and 'about' as a conventional meta tool, not a verb mismatch.

Tool Count5/5

Seven tools is well within the ideal 3-15 range. Each tool serves a distinct purpose: about for discovery, two resolvers for different identifier types, two paid monitors for different investor categories, one raw filing tracker, and one news search. No redundant or filler tools.

Completeness4/5

The tool set covers the core workflow: identifying companies (lookup_corp_code, resolve_stock_code), tracking raw filings (track_korean_filings), monitoring specific investor types (monitor_activist_investors, monitor_foreign_holders), and industry news (search_korean_industry_news). Minor gaps exist, such as no direct company profile/financial statements tool, and the paid monitor tools require licenses, but the surface is reasonably complete for its stated niche.

Resources