Skip to main content
Glama

의약품·영양제 금지성분·반입 제한

check_drug_import
Read-only

성분명·제품명(한·영)으로 마약류(마약·향정신성의약품·대마)·마약류 원료물질·국내 전용 성분 여부를 대조하고, 휴대 반입/직구와 수량을 자가사용 인정기준(6병·3개월분)과 비교해 판정합니다.

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": {
      "product_name": "<product_name>"
    },
    "name": "check_drug_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNo수량 단위(병·정·캡슐 등)
limitNo
channelNounknown
purposeNo
quantityNo수량(병·정 등). 6병 기준과 대조
ingredientNo성분명을 따로 넘길 때(있으면 product_name 보다 우선)
prescriptionNo처방전 보유 여부(소명자료 힌트)
product_nameYes성분명 또는 제품명(한글·영어 모두 가능, 예: '졸피뎀', 'Zolpidem', 'Adderall')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context by stating that the output is a judgment (판정) rendered against a defined self-use threshold, not a raw lookup. It does not disclose how the judgment is presented, what caveats apply, or that results may need legal-basis follow-up.

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?

It is a single dense sentence with the check target front-loaded before the threshold comparison, and no filler. The length is justified by the amount of scope conveyed, though the clause stacking makes it slightly harder to parse at a glance.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, open-world advisory tool with no output schema, the definition covers the core matching logic and the threshold rule but leaves the remaining parameters (prescription, limit, unit, purpose) and the shape of the verdict unexplained. It also gives no hint about escalating to legal-basis or case-assessment siblings when a prohibited ingredient is found.

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?

The definition adds meaning beyond the schema for the key parameters: ingredient/product_name are matched against narcotic and domestic-only ingredient lists, channel is framed as 휴대 반입 vs. 직구, and quantity is explicitly tied to the 6-bottle/3-month standard. It does not explain prescription, limit, purpose, or unit, which keeps it from a 5 given 63% schema coverage.

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?

The definition specifies a concrete verb (대조/판정) and a concrete resource scope (마약류·마약류 원료물질·국내 전용 성분, plus carry-in/online purchase quantity against the 6-bottle/3-month self-use standard), so an agent can distinguish it from a general labeling or food/cosmetics check. It does not name which sibling to use instead, so it falls short of the highest clarity level.

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 definition implies when the tool applies by naming the decision it makes (narcotic status + self-use quantity threshold), and the channel/quantity mention hints at carry vs. online shipping cases. However, it never explicitly distinguishes itself from likely alternatives such as assess_import_case, check_food_cosmetics, or get_legal_basis, leaving selection to inference.

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.