Skip to main content
Glama

기업지원금 진단 v1

subsidy_pack__diagnosis_v1__generate

Composite subsidy diagnosis v1: runs the work24 사업주 사전진단 sweep (one step covering every gated 지원사업) plus opendata nts.status, then reports which 지원금 the workplace may apply for. The work24 leg replays a logged-in session. No account_link_id is needed here: each step finds its own institution link. Verdicts keep work24's four raw states: 조사후결정/오류 are reported as undetermined, never folded into eligible the way the work24 screen does. If computed is null the result could not be assembled: read computed_error for the reason and do not present the result as complete. Two shapes carry that case: this envelope with partial set to true (we fetched everything - the legs hold it - but could not calculate), or an error whose data carries the same envelope. partial is true whenever the result is incomplete, whether a leg failed or the calculation did. Files: a document generated from this result, as PDF 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 pack_run_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. 호출마다 토큰 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": "subsidy_pack__diagnosis_v1__generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
biznoNo10-digit business registration number for nts.status
notice_fieldNo공고 지원 분야(선택). 금융, 기술, 인력, 수출, 내수, 창업, 경영, 기타 가운데 하나. 비우면 전 분야의 공고를 함께 봅니다.
output_formatsNoOptional. Also return this result as a file (PDF) in artifacts[] of the result. Omit it for data only.
programme_keysNoOptional subset of catalogue programme keys; omit to diagnose every 사전진단 사업.
idempotency_keyNoOptional outer idempotency key; leg keys are derived deterministically from this value.
notice_hashtagsNo공고 해시태그(선택). 지역이나 업종 같은 낱말 목록이며 하나라도 맞는 공고를 고릅니다(예: 서울, 제조업). 낱말 안에 공백은 넣지 않습니다.
application_yearNo신청시작연도 (defaults to the current year)
business_management_noNo고용보험 사업장관리번호. Omit to use the number stored at login; supply it when the company has more than one workplace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the work24 leg replays a logged-in session, that each call consumes a token and creates an XBOSS job, that the call is not purely read-only, and how raw work24 states map into verdicts (조사후결정/오류 become undetermined, never eligible). It also documents the two partial/computed_error envelope shapes, artifact retention (7 days) and download-link lifetime (15 minutes), plus the irrecoverable recovery_receipt for anonymous results.

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 purpose is front-loaded in the first sentence, but the body is dense and mixes English with long Korean boilerplate about token consumption and XBOSS job creation. The multi-sentence receipt/partial-envelope digressions are relevant yet could be tightened considerably.

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?

For a complex composite with 8 parameters and no output schema, the description covers the result envelope (computed, computed_error, partial), artifacts, and recovery paths well. It still does not sketch the per-programme verdict structure an agent would receive, leaving the shape of the primary payload partly implicit.

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, but the description adds real meaning for output_formats (a PDF artifact in artifacts[] with a 15-minute download_url and 7-day retention) and explains why no account_link_id is required. Remaining parameters such as programme_keys and notice_hashtags are left to the schema.

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?

Opens with a specific verb+resource: it runs the work24 사업주 사전진단 sweep plus opendata nts.status and reports which 지원금 the workplace may apply for. Naming the two underlying legs distinguishes it from the raw sibling work24__subsidy__diagnosis__search and opendata__nts__status without requiring the schema to be opened.

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?

Gives clear operative context (no account_link_id needed, each leg resolves its own institution link) and explicit follow-up routing: call xdata__job__result with pack_run_id when a download link has expired. It stops short of stating when to prefer this composite over calling the individual source tools directly, so there is no true exclusion or alternative comparison.

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