Skip to main content
Glama

허가 원문 조회

get_permit
Read-onlyIdempotent

Fetch full MFDS authorization text for a drug or medical device using its product ID, so advertising claims can be checked against approved indications and warnings.

Instructions

제품 하나의 식약처 허가 원문을 자르지 않고 가져온다. 광고 문구를 대조할 근거로 쓴다. 의료기기: 사용목적, 등급, 모델명. id는 품목허가번호. 의약품: 효능효과, 용법용량(선택: 사용상의 주의사항), 전문/일반 구분. id는 품목기준코드(ITEM_SEQ). 취소·취하 상태나 전문의약품이면 경고를 함께 준다.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "get_permit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYessearch_products가 돌려준 식별자
typeYesdevice = 의료기기(사용목적 기준), drug = 의약품(효능효과 기준)
include_precautionsNo의약품 사용상의 주의사항 포함 여부, 기본 false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds genuinely new behavior by promising the text is returned untruncated and that warnings are surfaced for cancelled/withdrawn status or prescription-only drugs. Rate limits, auth, and error behavior are unstated, keeping 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.

Conciseness5/5

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

Front-loaded first sentence states the action and the anti-truncation guarantee, then a compact per-type block enumerates fields and id formats, closing with the warning behavior. Every line carries distinct information; nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return-value burden and discharges it by listing the fields returned for each type plus the warning surface. Combined with full schema coverage and annotations, an agent has everything needed to call this correctly.

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 beyond it: the id is a 품목허가번호 for devices versus a 품목기준코드 (ITEM_SEQ) for drugs, and the optional precautions field is tied explicitly to the drug type. That disambiguates which identifier form to pass for each enum value.

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 specific verb and resource — fetches the full, untruncated MFDS approval text for exactly one product — and implicitly contrasts with search_products, which supplies the id. The per-type field breakdown (device vs drug) makes the returned content unmistakable, so an agent can distinguish this from sibling 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?

Gives a concrete usage context: use it as evidentiary basis when cross-checking advertising claims, and clarifies that the id comes from a prior search_products call, establishing the correct call order. It stops short of naming an explicit exclusion or contrasting with compare_products, so it is clear but not fully routing.

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

Deploy Server

Other Tools