Skip to main content
Glama

treasury_share

Aggregate and cross-verify treasury share events—decisions and execution reports—for Korean stocks, including acquisition, disposal, cancellation, and trust cycles.

Instructions

desc: 자기주식 이벤트 통합. 결정 5종(사전 의도) + 결과보고서 4종(사후 집행) 통합 집계. 주주환원 검증 = 결정만 X, 실제 집행 cross-check. when: 자사주 취득·처분·소각·신탁 이력·규모. 결정↔결과 사이클 매칭으로 집행 검증. rule: 9 source 병렬 — Decisions: tsstkAqDecsn(취득)/tsstkDpDecsn(처분)/tsstkAqTrctrCnsDecsn(신탁체결)/tsstkAqTrctrCcDecsn(신탁해지)/소각결정. Executions: 취득결과/처분결과/신탁취득상황/신탁해지결과 보고서. ACODE 본문 파싱. 사이클 매칭은 "주요사항보고서 제출일" / "신탁계약 체결일" ↔ decision rcept_dt. 종류별: 보통주 vs 종류주식(우선주·기타주식·RCPS 등 통합) — 결정/결과 모두 amount_common_krw/amount_preferred_krw로 분리(결과는 복수 종류 시 ACODE가 보통주만 잡는 것을 일별 합산 보정). scope: summary 모든 events + breakdown + cycle 매칭 / annual 사업보고서 연간 누적 잔고 ref: value_up, ownership_structure, dividend, evidence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
scopeNosummary
formatNomd
companyYes
end_dateNo
start_dateNo
lookback_monthsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Without annotations, the description discloses the tool's behavior: it integrates 9 source types, splits by common/preferred shares, performs cycle matching, and offers two scopes. It does not mention rate limits or auth needs, but covers key behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long and detailed, mixing languages and some redundancy. It is front-loaded with the purpose but includes extensive technical detail that could be streamlined for clarity.

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 complexity (7 params, no annotations, output schema exists), the description covers the tool's data sources and scope but lacks parameter-specific guidance and interaction details, leaving some gaps for effective use.

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%, so the description must compensate. Only the 'scope' parameter is explained ('summary' vs 'annual'). Other parameters (year, dates, lookback_months, format) are not described, leaving significant gaps.

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 integrates treasury share events, listing 5 decisions and 4 executions with cross-checking. It distinguishes from siblings like dividend, ownership_structure, and value_up by mentioning them as references.

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 'when' section specifies use cases: treasury stock acquisition, disposal, cancellation, trust history, and cycle matching for execution verification. However, it does not explicitly state when not to use the tool or suggest alternative tools.

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/MarcoYou/open-proxy-mcp'

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