Skip to main content
Glama
Sign In

APICK

by app.apick
OverviewDiscussionsAdmin

재무 건전성 분석

dart_financials
Read-only

Compute Korean company financial health: margins, debt and current ratios, ROE/ROA, year-over-year growth and distress flags. 재무제표 계정에서 영업이익률·순이익률·부채비율·유동비율·ROE·ROA와 전기 대비 성장률을 계산하고 적자·과다부채 신호를 표시합니다. 응답은 summary·metrics·distribution·flags·insights 이며 계정 원문 목록은 제공하지 않습니다. [호출당 50포인트]

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": {
      "corpCode": "<corpCode>",
      "bsnsYear": "<bsnsYear>"
    },
    "name": "dart_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
fsDivNo연결(CFS)/개별(OFS) 구분 (기본 CFS)
bsnsYearYes사업연도 (YYYY, 2015년 이후)
corpCodeYes기업 고유번호 (8자리)
reprtCodeNo보고서 코드 (11011 사업, 11012 반기, 11013 1분기, 11014 3분기 / 기본 사업)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover readOnly/openWorld; the description adds genuinely new behavioral context absent from them: the exact response envelope (summary/metrics/distribution/flags/insights), the explicit omission of raw account lists, and a per-call cost of 50 points. It stops short of saying what happens when a year has no data or how partial fiscal years are handled.

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?

Purpose is front-loaded in the first clause and the response-shape and cost notes follow logically. The English/Korean duplication is redundant for a bilingual audience but each version is lean, and no sentence is filler beyond that mirroring.

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 return fields does real work and the cost disclosure matters for a metered API. Remaining gaps are minor: no mention of pre-2015 year limits despite the schema constraint, and no behavior when financials are unavailable.

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 description coverage is 100% with enums documented for fsDiv and reprtCode, so the schema carries all parameter meaning. The description contributes nothing about parameters, so the baseline 3 applies.

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?

States a specific verb and resource ('Compute Korean company financial health') and enumerates exactly which metrics are produced: margins, debt and current ratios, ROE/ROA, YoY growth, distress flags. It implicitly distances itself from the raw-statement sibling by declaring '계정 원문 목록은 제공하지 않습니다', though it never names corp_finance directly.

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 note that raw account lists are not returned hints that corp_finance is the alternative for statement-level data, but no sibling is named and there is no explicit 'use this when…' statement. The 50-point cost line gives a rough budget signal but not a usage rule.

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

All APICK 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