Hedgenaru Korean Stocks

종목 찾기

search_stocks

Read-onlyIdempotent

한국 상장 종목(KOSPI·KOSDAQ)을 이름·초성·영문명·코드로 찾아 6자리 종목코드를 돌려준다. 다른 도구에 넣을 symbol 을 모를 때 먼저 부른다.

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": {
      "query": "<query>"
    },
    "name": "search_stocks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	최대 결과 수 (기본 10, 최대 30)
`query`	Yes	종목명 일부, 초성(ㅅㅅㅈㅈ), 영문명, 코드 앞자리

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 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/non-destructive/non-open-world, so the safety profile is covered. The description adds value beyond them by naming the market scope (only KOSPI·KOSDAQ) and the exact return shape (6-digit code), though it says nothing about ambiguity or multi-match handling.

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?

Two short sentences, zero padding, with the capability and the routing instruction both front-loaded.

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 two-parameter lookup tool with no output schema, the description supplies the market scope and return type an agent needs. It could optionally clarify whether multiple matches are returned as a list, but nothing essential is missing.

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?

Schema coverage is 100%, and the schema documents both the query forms and the limit bounds (default 10, max 30). The description's mention of name/초성/English/code largely restates schema content, so it adds little new parameter meaning.

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?

States a specific verb (찾아) and resource (한국 상장 종목 KOSPI·KOSDAQ), the lookup keys (이름·초성·영문명·코드), and the concrete return value (6자리 종목코드). This clearly positions it as the symbol-resolver relative to the sibling data tools, which all consume a symbol.

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?

Explicitly tells the agent when to call it: before other tools when the symbol is unknown ("symbol 을 모를 때 먼저 부른다"). There is no explicit when-not or named alternative, but for a resolver tool the positive condition is the operative one.

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

All Hedgenaru Korean Stocks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?