Skip to main content
Glama
Sign In
koreanpulse

koreanpulse

by whdrnr2583-cmd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Resolve KRX 6-digit ticker to DART corp entry

resolve_stock_code
Read-onlyIdempotent

Transform a 6-digit Korean stock code into company name and corporate code for DART filings and industry news.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stock_code": "<stock_code>"
    },
    "name": "resolve_stock_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
stock_codeYes
license_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds 'Free tier', which hints at rate limits or accessibility, providing extra context beyond annotations for a simple lookup tool.

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 two sentences: the first concisely defines the tool, the second gives usage guidance with examples. It is front-loaded, every sentence adds value, and no words are wasted.

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?

For a simple resolver with an output schema, the description covers the main purpose, usage context, and downstream applications. It does not detail error handling or rate limits, but overall it is sufficient for the tool's simplicity.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the two parameters (stock_code and license_key). The example values for stock_code are helpful, but license_key is not mentioned, and no parameter details are added beyond the schema.

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 resolves a KRX 6-digit ticker to a DART corp entry, provides examples, and explains the output (company name + corp_code). It distinguishes itself from siblings like lookup_corp_code and search_korean_industry_news by specifying the purpose and downstream use.

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 says 'Use this tool when the user provides a 6-digit Korean stock code... and you need the company name + corp_code'. This gives clear context for when to use it, though it does not mention when not to use or list alternatives.

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

Deploy Server

Other Tools