Skip to main content
Glama

국내 주식·채권 MCP (Korea Stocks & Bonds)

분기 실적 시즌

earnings_season
Read-onlyIdempotent

[국내 주식 + 채권 MCP FinQuest] 분기 실적 시즌 — 한 분기(기본: 가장 최근 보고 분기)에 실적을 낸 전 종목을 모아 합계(매출·영업이익 YoY, 증익 회사 비율, 흑자전환·적자전환 수), 업종별 영업이익 증감 상·하위, 그리고 종목 목록(영업이익·매출·순이익 YoY·QoQ, 이익률, 제출일). kind 로 증익·감익·흑자전환·적자전환만, by 로 정렬. '이번 분기 실적 좋은 회사', '흑자전환한 회사', '3분기 실적 시즌 어땠어' 같은 질문에.

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": "earnings_season"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNo정렬 — op_diff(영업이익 증감액, 기본)·op_yoy·rev_yoy·ni_yoy·op_qoq·rev_qoq·op·rev·ni·opm·filed(최근 제출 순)
kindNoall(기본) · growth(영업이익 증가) · decline(감소) · turnaround(흑자전환) · to_loss(적자전환)
limitNo
themeNo테마 (예: '방산', '2차전지')
marketNo
periodNo분기 — '2026Q3', '3Q26', '2026-09'. 생략하면 가장 최근 보고 분기
industryNo업종 이름 일부
min_mcapNo시가총액 하한(억원). 증감률 정렬은 기본 1,000억

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the bar is lower, and the description still adds real behavior: the default period is the most recently reported quarter, the result set is unfiltered by default (전 종목), and the response is a composite of aggregate totals, industry extremes, and a list — none of which annotations convey. It omits pagination/limit behavior and any hint about data lag or partial-quarter coverage.

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?

Front-loaded with the tool's identity and default quarter, then the output composition, then filters — a logical order. The middle sentence is a long parenthetical enumeration that is dense but each clause carries filter or output information, so little is 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?

With no output schema, the description's enumeration of what comes back (totals, YoY, ratio of companies with profit growth, turnaround counts, industry top/bottom, per-stock rows with 제출일) is exactly the missing piece an agent needs. Remaining gaps are minor: default for `limit`, and how theme/market/industry interact with the aggregate totals.

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 75%, so the baseline applies. The description restates `kind` (증익·감익·흑자전환·적자전환) and `by` (정렬) semantics that the schema's enum descriptions already spell out, and it adds little on limit, theme, market, or industry beyond their existing descriptions.

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 concrete resource and scope: all stocks that reported earnings in one quarter, plus aggregate YoY figures, industry-level operation-profit top/bottom movers, and a per-stock table. The verb ('모아' collect/summarize) and the enumerated outputs make it distinguishable from the sibling earnings/earnings_calendar tools without opening a schema.

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?

Three example user questions ('이번 분기 실적 좋은 회사', '흑자전환한 회사', '3분기 실적 시즌 어땠어') explicitly map intents to this tool, which is strong selection guidance. It does not, however, say when to prefer the sibling earnings or earnings_calendar instead, so no exclusion is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources