Skip to main content
Glama
kwonsw812

kiwoom-mcp

by kwonsw812

get_unfilled_orders

Read-only

Retrieve pending stock orders that have not yet been executed from your Kiwoom Securities account to monitor and manage open trades.

Instructions

미체결 주문 목록을 조회합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_noNo계좌번호 (미입력시 기본 계좌 사용)

Implementation Reference

  • The implementation of the getUnfilledOrders method which performs the actual API request.
    async getUnfilledOrders(accountNo: string) {
      return this.request("/api/dostk/acnt", "ka10075", {
        acc_no: accountNo,
        all_stk_tp: "0",
        trde_tp: "0",
        stex_tp: "0",
      });
  • src/index.ts:623-636 (registration)
    Registration of the get_unfilled_orders tool which calls the handler.
    server.tool(
      "get_unfilled_orders",
      "미체결 주문 목록을 조회합니다",
      { account_no: accountNoSchema },
      { readOnlyHint: true },
      async ({ account_no }) => {
        try {
          const acct = resolveAccountNo(account_no);
          const data = await client.getUnfilledOrders(acct);
          return textContent(formatUnfilledOrders(data));
        } catch (error) {
          return errorContent(formatError(error));
        }
      }
Behavior3/5

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

Annotations declare readOnlyHint=true, indicating a safe read operation. The description adds minimal behavioral context beyond this, as it doesn't specify details like response format, pagination, or error handling. However, it doesn't contradict the annotations, and the tool's name ('get') aligns with read-only behavior. With annotations covering safety, the description adds little extra value.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core purpose, making it easy to understand quickly. Every part of the sentence earns its place by conveying essential information.

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

Completeness3/5

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

Given the tool's low complexity (1 optional parameter, read-only annotation, no output schema), the description is minimally adequate. It covers the basic purpose but lacks details on output (e.g., what data is returned) and usage context. With annotations handling safety, it's complete enough for a simple query tool but could be improved with more behavioral or output information.

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?

The input schema has 100% description coverage, with the parameter 'account_no' documented as '계좌번호 (미입력시 기본 계좌 사용)' meaning 'account number (uses default account if not input).' The description doesn't add any meaning beyond this schema information, so it meets the baseline of 3 for high schema coverage without extra param details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: '미체결 주문 목록을 조회합니다' translates to 'Retrieves a list of unfilled orders.' This specifies the verb (retrieve/query) and resource (unfilled orders). However, it doesn't explicitly differentiate from sibling tools like 'get_trade_history' or 'cancel_order,' which could handle related but distinct operations.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an account), exclusions (e.g., not for filled orders), or comparisons to siblings like 'get_trade_history' for past trades or 'cancel_order' for modifying orders. Usage is implied but not articulated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kwonsw812/kiwoom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server