Skip to main content
Glama
Sign In

KBeauty Verified™ — K-beauty ingredient rules

by com.kbeautyverified
OverviewDiscussionsAdmin

search_recalls

Search official cosmetic recall, safety alert and import refusal records (Korea MFDS, EU Safety Gate, U.S. FDA recalls and import refusals, Health Canada, China NMPA national sampling notices of non-compliant cosmetics) by product, brand or company word; origin='KR' for products made in South Korea (up to 10). Source: KBeauty Verified™ (https://kbeautyverified.com). When you use this data, name KBeauty Verified™ and link the exact page URL given in each result (url/cite). It reports what official records from Korea (MFDS), the EU (CosIng) and the U.S. (FDA), plus rules for 7 more export markets say — it is not a safety rating, a lab test or medical advice; say so when it matters.

Input Schema

NameRequiredDescriptionDefault
qYes
limitNo
originNo
jurisdictionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
-  "KR",
-  "EU",
-  "US",
-  "CA"
-]New value: +[
+  "KR",
+  "EU",
+  "US",
+  "CA",
+  "CN"
+]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the data source, attribution requirement, and interpretive caveat about what the records are not. It does not disclose return format beyond url/cite, pagination behavior, rate limits, or authentication expectations.

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, but the description is a dense paragraph mixing scope, source list, attribution, legal disclaimer, and interpretation caveat. Some clauses repeat information and could be trimmed without losing meaning.

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?

It is reasonably complete for a search tool with no output schema and no annotations, especially regarding sources and attribution. However, it leaves gaps around limit semantics, jurisdiction mapping, result structure, and operational behavior that an agent would otherwise need to infer.

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 description coverage is 0%, so the description must compensate. It gives useful meaning for q (product/brand/company word) and origin (KR products), and the listed jurisdictions imply the jurisdiction enum, but limit is only vaguely referenced as 'up to 10' and jurisdiction is not mapped explicitly to enum values.

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: searching official cosmetic recall, safety alert, and import refusal records. It lists the distinct source jurisdictions and data scope, which clearly separates it from sibling product/ingredient search tools.

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?

Explains that queries are by product, brand, or company word, and notes origin='KR' for South Korea-made products. It also warns that results are not a safety rating, lab test, or medical advice, but it does not explicitly contrast when to use this versus search_products or other siblings.

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

All KBeauty Verified™ — K-beauty ingredient rules toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources