Skip to main content
Glama

koreanpulse

by io.github.whdrnr2583-cmd

Resolve Korean company name to DART corp_code

lookup_corp_code
Read-onlyIdempotent

Korean company name → DART corp_code resolver. 117K+ entities indexed (KOSPI + KOSDAQ + KONEX + unlisted). Free tier.

Use this tool when the user mentions a Korean company by name (Korean characters or English/romanized) and you need the DART corp_code as a precondition for track_korean_filings, monitor_activist_investors, or monitor_foreign_holders. Also use to disambiguate same-name listed vs unlisted entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax matches to return.
queryYessubstring of the Korean corp name. Examples: "삼성전자", "현대차", "셀트리온".
license_keyNosubscription key. Required when license gate is enabled.
listed_onlyNoif True, only return companies with a KRX stock code.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety behavior is covered. The description adds valuable context about entity coverage (KOSPI, KOSDAQ, KONEX, unlisted), language support (Korean or English/romanized), and free tier availability. This goes beyond the structured annotations.

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 compact and front-loaded: one sentence states the core purpose, and one sentence gives usage guidance. Every sentence adds value, and there is no redundant restating of the title or schema.

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

Completeness5/5

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

Given the tool's moderate complexity, an output schema exists, and parameter descriptions are complete, the description fully covers purpose, scope, and usage context. It even mentions free tier and entity universe. There are no significant gaps for an agent to select and invoke this tool correctly.

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?

Schema coverage is 100%, so parameters are well-documented. The description additionally clarifies that query supports Korean characters or English/romanized names, which is not explicitly in the schema examples. It also hints at listed_only semantics through 'disambiguate same-name listed vs unlisted entities.'

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 specific verb-resource pair: 'Korean company name → DART corp_code resolver.' It clearly distinguishes this tool from siblings like resolve_stock_code by focusing on DART corp_code, not stock code. The mention of 117K+ entities and listed/unlisted coverage adds precision.

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 states when to use the tool: when a Korean company name is mentioned and a DART corp_code is needed as a precondition for track_korean_filings, monitor_activist_investors, or monitor_foreign_holders. It also mentions disambiguation use. It lacks an explicit 'do not use' statement or named alternative, but the use cases are clear enough.

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