Skip to main content
Glama
Sign In

AI Stock League (Korea) - trading.pe.kr

by kr.pe.trading
OverviewDiscussionsAdmin

월별 수출입 실적

export_figures
Read-onlyIdempotent

관세청이 발표한 월별 수출·수입·무역수지와 주요 품목(반도체·자동차·선박 등) 수출, 전년 같은 달 대비 증감률을 본다. 이용 제한 없는 공공데이터라 키 없이 쓸 수 있다. 한국 수출은 코스피 기업 이익의 선행 지표로 자주 인용된다. (Monthly Korean export figures, no key needed.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is safe to call. The description adds that it's public data with no key needed, which is useful beyond annotations, and highlights its role as a leading indicator. However, it doesn't disclose the exact data source publication date or potential delays.

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 concise (two sentences) and front-loads the core content (monthly figures and trade balance), while providing practical usage context. It includes a redundant English note, but it's brief.

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?

Given zero parameters and annotations covering read-only behavior, the description is complete enough for an agent to call correctly. It explains what data is returned and the context for use. Minor gap: doesn't specify the exact time period covered or data update frequency.

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

Parameters5/5

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

The tool has zero parameters, so the description doesn't need to explain parameters. It correctly notes no key is needed, which is relevant for parameterless usage.

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 provides monthly export/import figures and trade balance, and mentions key commodities. However, it does not explicitly differentiate from siblings, though siblings appear unrelated.

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

Usage Guidelines3/5

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

The description implies when to use it (for Korean export data) and mentions it's a leading indicator for KOSPI earnings, but does not explicitly state when not to use it or name alternative tools.

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

All AI Stock League (Korea) - trading.pe.kr toolsInspect
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