Skip to main content
Glama

재무 요약 조회

opendata__fsc__financials

공공데이터포털에 개방된 법인 요약재무제표(data.go.kr 15043459)를 법인등록번호로 조회합니다. 사업연도마다 별도와 연결 재무제표 행이 따로 오며 매출액, 영업이익, 당기순이익, 총자산, 총부채, 총자본, 자본금, 부채비율을 statements 에, 가장 최근 사업연도의 행을 latest 에 돌려줍니다. 사업자등록번호만 주면 법인등록번호를 찾아 조회하고 개인사업자이면 빈 결과에 그 사유를 담습니다. 별도 연동 없이 사용할 수 있습니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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

Input Schema

NameRequiredDescriptionDefault
crnoNo법인등록번호 13자리(하이픈 허용). crno 와 bizno 가운데 하나 이상.
biznoNo사업자등록번호 10자리(하이픈 허용). crno 가 없을 때 법인등록번호를 찾는 데 씁니다.
pageNoNo페이지 번호(선택, 기본 1).
bizYearNo사업연도 4자리(선택). 비우면 개방된 모든 사업연도를 돌려줍니다.
numOfRowsNo한 페이지 행 수(선택, 기본 100).
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description reinforces this by explicitly stating the call is not purely read-only because each call consumes one token and creates an XBOSS job. It adds genuinely non-schema behavior: 15-minute download links, 7-day file retention, recovery via xdata__job__result, and idempotency-key reuse rules. Much of the file/receipt paragraph is generic boilerplate shared across the pack, which keeps it below a 5.

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 core purpose and return shape are front-loaded well, but the middle section is a long block of generic artifact/receipt/idempotency boilerplate that partly duplicates the output_formats schema field. The final Korean paragraph about XBOSS jobs and token consumption feels appended rather than integrated.

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 correctly compensates by naming the returned fields and their grouping. With 7 parameters at 100% coverage the parameter story is complete, though pagination behavior (pageNo/numOfRows interaction, total counts) is left to the schema alone.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the crno-vs-bizno fallback outcome (empty result with reason for sole proprietors) and by mapping results into statements (per fiscal year, separate vs consolidated rows) and latest. It adds useful semantics about the consequences of the identifier choice that the schema merely hints at.

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 opens with a specific verb+resource: it queries the corporate summary financial statements opened on data.go.kr (dataset 15043459) by corporate registration number. It even names the returned containers (statements, latest) and the individual line items, so an agent can distinguish it from opendata__fsc__corp_outline and similar siblings without opening the 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?

It states that no separate integration/auth is needed, that bizno is only used to resolve a crno when crno is absent, that sole proprietors yield an empty result with a reason, and that output_formats is only for file output. It does not explicitly name a competing sibling tool or a when-not-to-use condition, so it stops short of full routing guidance.

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