Skip to main content
Glama

리콜 이력 조회

lookup_recall
Read-only

브랜드·모델명·제품명으로 국내 리콜 이력을 조회합니다. 로컬 인덱스(국표원 15040696) 우선, 없으면 소스 미연결을 그대로 알립니다.

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": {
      "brand": "<brand>"
    },
    "name": "lookup_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYes
limitNo
modelNo
categoryNo법정제품분류 키워드(예: '전지', '직류전원장치')
product_nameNo제품명·품목군 키워드(예: '미니 선풍기')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read safety, but the description adds real behavior the schema cannot express: a local index (KATS 15040696) is queried first, and a missing source is surfaced as a plain notice rather than an error. It does not cover result shape or whether an empty result differs from an unreachable source, which keeps it short of 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?

Two short sentences with no filler: the lookup scope is front-loaded, then the fallback behavior. Nothing is repeated from the title or annotations.

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 a 5-parameter, annotation-light lookup with no output schema, the description explains search keys and degraded-source behavior but leaves limit semantics and combination-of-filters logic unexplained. Adequate to start a call, not to predict the result set.

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?

With only 40% schema coverage, brand, model, and limit are undocumented in the schema; the description only implies brand/model act as match keys. The limit cap (max 20, default 5) and how brand vs. model vs. product_name are combined are never clarified.

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?

States a specific verb and resource: lookup of domestic recall history, keyed by brand, model, or product name. That is clearly distinct in domain from siblings like lookup_hs_requirements or check_kc_certification, though the description never explicitly contrasts itself with them.

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 searchable keys (brand/model/product name) imply when to reach for this tool, and the fallback sentence implies it is the first stop for recall checks. There is no explicit when-not guidance, no prerequisites, and no pointer to an alternative if a source is unconnected.

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.