Skip to main content
Glama

허가 범위 비교

compare_products
Read-onlyIdempotent

Retrieve official Korean authorization text for 2–5 similar drugs or medical devices and view approved indications side by side to see how your product's approved scope differs from competitors'.

Instructions

같은 종류의 제품 2~5개의 허가 원문(의료기기 사용목적, 의약품 효능효과)을 나란히 가져온다. 자사·경쟁 제품의 허가 범위 차이를 볼 때 쓴다.

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>",
      "ids": "<ids>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYessearch_products가 돌려준 식별자 목록
typeYesdevice = 의료기기(사용목적 기준), drug = 의약품(효능효과 기준)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description need not re-establish that this is a safe read. It does add real value by disclosing what content comes back — the raw permitted scope fields compared per product type — which matters since no output schema exists. It stops short of describing ordering of results, behavior on type mismatch or invalid ids, or output shape.

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?

Two sentences, zero filler: the first defines the operation and its scope, the second gives the triggering situation. Everything is front-loaded and nothing is repeated from the title or schema.

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 two-parameter read tool this is nearly complete — it says what is fetched, the cardinality constraint, the type dimension, and the intended decision it supports. The remaining gap is edge-case behavior (mismatched types within `ids`, or ids that are not permits) and any hint about result ordering.

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 coverage is 100% and the schema already documents both `ids` (identifiers returned by search_products, 2–5 items) and `type` (device vs drug with the basis for comparison). The description's '2–5 products of the same type' mirrors the schema constraints rather than adding meaning, so the baseline 3 is appropriate.

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 description gives a specific verb and resource — it pulls the permit originals (intended use for devices, efficacy/effects for drugs) for 2–5 products of the same type and places them side by side. That is far more concrete than a restatement of the name/title, and the 'compare N products' framing separates it from the single-record get_permit and the lookup-oriented search_products, though it never names either sibling explicitly.

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 the use case clearly: when you want to see differences in permitted scope between your own and competitor products. There is no explicit exclusion or named alternative ('for a single product's permit, use get_permit'), so the routing is implied by the comparison framing rather than spelled out.

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